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
Fix zipWith to work concurrently according to the stream type #158
Comments
I suppose this is complementary to the existing |
zipAsyncWith makes sure that the actions from both the streams being zipped are executed concurrently, once it has the two items to zip, then it uses zipWith to zip the two items. So only one zip happens at a time. In case of ahead/async streams we can have multiple zips going on at the same time. |
@adithyaov if this is fixed then you can close it. |
We can possibly have |
zipWith
andzipWithM
currently work serially. They should instead work according to the stream type. For example, if the stream type isAsync
then they can zip multiple pairs concurrently out of order. For testing, one use case of this is mentioned in #100 .The fix is simple, we need to use
consM
to build the stream, just like we do in concurrentmapM
. We will just have to test it, that it works as expected.cc @naushadh
The text was updated successfully, but these errors were encountered: