Check expr type for expr;step in s![] macro at compile time, and remove AxisSliceInfo::step_by #943
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.
Before, if the
expr;step
notation was used with an index as theexpr
, e.g.s![4;2]
, the macro would panic at runtime. Now, it errors at compile time. This is accomplished by converting theexpr
to aSlice
before converting it into the finalAxisSliceInfo
.The
AxisSliceInfo::step_by
method is awkward because it panics for all cases except theSlice
variant. This method is no longer necessary because thes![]
macro now callsSlice::step_by()
instead.