Fix undefined behavior reported by miri when reading or writing slices #351
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.
Many methods in the slice or array api take a pointer to the first element and then use that pointer to read or write multiple lanes.
This is undefined behavior according to miri since pointer is only valid for a single element. The fix is to use the
as_ptr
/as_mut_ptr
methods of the slice, which gives a pointer to the whole slice and also leads to nicer code.