Dispatch on traits in iterate for AbstractArrays and types that wrap AbstractArrays #41968
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.
An attempt at using traits in
iterate
forAbstractArray
s (Fixes #41945), which makes iteration for wrapper types (eg.OffsetArray
s) use the sameiterate
method used for the parent array, consequently obtaining the same performance. Array wrapper types may opt-in to the iteration behavior of the parent through the traitIterationStyle
, for example asBy default they will fall back to the
iterate
method forAbstractArray
s, which is the present behavior.A comparison of the performance without using the trait and with it (see #41945 for other examples):
Without defining the trait for
OffsetArray
s:With the trait defined:
I would love some feedback on this as it is a somewhat large change, although there seems to be a significant performance benefit to this.