Unpack nested IteratorAggregate objects for Count #2689
Merged
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.
From my previous comment in #2642 (comment):
This PR adds logic to unwrap nested IteratorAggregate objects until we encounter a Traversable that is not an IteratorAggregate instance. This ensures that generator detection (#2149) and internal Traversables (#2642) are properly detected before we attempt to restore the Iterator's position after counting (#1125).
In a separate commit, the PR also adds missing regression tests for Count's handling of non-nested IteratorAggregate objects.