change for i in 1:length(a) to i in eachindex(a) (continuing #10858) #12788
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.
Continuing the changes made in #10858 and #8432, this changes
for i = 1:length(a)
tofor i in eachindex(a)
throughout Base, and adds missingeachindex
methods forNumber
andTuple
types (which are required for generic code).There should be no performance penalty to this, since in most cases
eachindex(a)
inlines to1:length(a)
anyway. But since usingeachindex(a)
in loops is now the preferred style, it seemed best to do it consistently in Base, both to establish the habit and to catch any problems.