-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CoflatMap for Sync #97
Comments
👍 I don't see the harm |
Closed
@ChristopherDavenport do you think this is still relevant, are you interested in doing some proposal or should we close it? Spring cleaning 🙂 |
I think we can remove it. The consensus seems to be, if we want it for a type, it should use the method in it for cats. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that any Applicative can form a CoflatMap
This personally strikes me as a useful value to have perhaps to generalize an Action describing an Action, but more so in effect suspension for things that implement Sync like Fs2's Stream which in order to get concurrency
Stream(1,2,3).map(i => Stream(i)).joinUnbounded
could instead utilizedStream(1,2,3).coflatten.joinUnbounded
however I think this is a generally good thing to have available. The PR linked from cats can bring this easily for allSync
with the next Milestone.Would this be something you would entertain?
The text was updated successfully, but these errors were encountered: