Fix collection-optimized paths to be at iteration-time #946
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.
This PR fixes #943.
It fixes the optimised path in the following operators for when the source is a collection:
AssertCount
CountDown
FallbackIfEmpty
PadStart
SkipLast
TakeLast
All of the above operators have deferred execution semantics, but they were binding to the source collection count when invoked and not when the resulting sequence was iterated. Consequently, if the source collection was updated before iteration, the (cached) count and the resulting sequence would be incorrect.
Tests have been added to avoid regressions in the future.
Some tests were removed because the optimisations they were exercising couldn't be maintained anymore. For example, if
AssertCount
could determine that the source was a collection and had the right count, then it would return the source reference as-is. Now, the count is asserted when iteration start.