perf: override default implementation in ArrayIter with dedicated null/non-nullable versions
#8697
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.
Which issue does this PR close?
N/A
Rationale for this change
Improve the performance of array iterator functions by skipping null checks on non nullable
What changes are included in this PR?
override
ArrayIterdefault function implementation with one that check if there are nulls or not:nth/nth_backlastcountfor_eachfold/rfoldallanyfind_mapfind/rfindpartitionposition/rpositionthis implement all functions in
Iterator/DoubleEndedIteratorthat the default implementation is either using some base function that we can't implement in stable (e.g.try_fold) or the implementation is naive (e.g. callingnext()a lot of times)Are these changes tested?
Yes, a LOT
Are there any user-facing changes?
Nope
This include the following fix which was found while working on this:
ArrayIterdoes not report size hint correctly after advancing from the iterator back #8728