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 is some ground work for supporting index types like those in Dex.
I've added two fields to
OptionallyStaticUnitRange
andOptionallyStaticStepRange
that allow manually eliding bounds checks for the first and last values in a range. These fields are not intended to be used directly by most users. Rather, the goal is to have functions that correspond to similar syntax as those in Dex (i..
,..i
,i<..
, etc.), with a specific collection as a point of reference. I haven't yet decided what the actual method names should be to mirror this functionality. Perhaps something like,all_indices(A, >(i))
? @AriMKatz, perhaps you have some ideas on this?I've included benchmarks below just to demonstrate that this does provide the performance improvement you'd expect when skipping bounds checking. Providing formal methods for constructing these could also help avoid overuse and abuse of
@inbounds
.