fix Flow.take waiting for n+1 elements instead of terminating at n#220
Merged
fix Flow.take waiting for n+1 elements instead of terminating at n#220
Conversation
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously,
take(n)would hang forever if the source had exactly n elements. This happened because it tried to read one more element (to check if it should break) even after taking all n elements it needed.For example,
take(3)on a 3-element stream would:Now it breaks right after taking the n-th element, without trying to read more:
Added test
shouldBreakImmediatelyAfterTakingNElements()that verifies we process exactly 3 elements when callingtake(3), not 4.