fix(zip): zip operators and functions are now able to zip all iterable sources #5688
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.
Resolves an issue I outlined in #4304. Basically, once upon a time, I had a "brilliant" idea to have iterators iterated "as needed" during a zip operation. There are a few consequences to this, but the nastiest one is that you could not use zip with all-iterable sources. It also doesn't jive with the push-based nature of this library. This PR fixes all of that.
BREAKING CHANGE:
zip
operators will no longer iterate provided iterables "as needed", instead the iterables will be treated as push-streams just like they would be everywhere else in RxJS. This means that passing an endless iterable will result in the thread locking up, as it will endlessly try to read from that iterable. This puts us in-line with all other Rx implementations. To work around this, it is probably best to usemap
or some combination ofmap
andzip
. For example,zip(source$, iterator)
could besource$.pipe(map(value => [value, iterator.next().value]))
.fixes #4304