Add termination strategies for ZStream#merge #3543
Merged
Conversation
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
|
|
|
@luis3m Thanks, the approach looks great! Nice work! Can you check why the tests are flaky? |
|
That's great @luis3m. So will merge this as soon as the TestClock changes are in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As discussed on Discord, add termination strategies for
ZStream#merge.mergeTerminateLeft: given stream A and B, new produced stream C will terminate as soon as A terminatesmergeTerminateRight: given stream A and B, new produced stream C will terminate as soon as B terminatesmergeTerminateEither: given stream A and B, new produced stream C will terminate as soon as either A or B terminatemergewith no strategy specified: current behavior, given stream A and B, new produced stream C will terminate when both A and B terminate