Skip to content
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.

Sign up for GitHub

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

Jump to bottom

concatMap() is not a good solution if you need concurrency #2

Open
Mariovc opened this issue Dec 26, 2017 · 0 comments
Open

concatMap() is not a good solution if you need concurrency #2

Mariovc opened this issue Dec 26, 2017 · 0 comments

Comments

@Mariovc
Copy link

Mariovc commented Dec 26, 2017 •
edited

In the article about flatMap() vs concatMap() it should be mentioned that the second one doesn't run the tasks in parallel but in sequence so the solution is not a real replacement for a flatMap (at least in my case).
I suggest to use concatMapEager() if we need the results to be strictly in order.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mariovc and others