hybrid-array: make ArraySize
an unsafe trait
#914
Merged
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.
It's used when checking the lengths of slices match an array size prior to using a pointer cast to convert types.
If someone were to make their own
typenum::Unsigned
type and implArraySize
for it with anArrayType
whose size does not matchUnsigned::USIZE
, that would be UB.Really
ArraySize
is not intended for downstream crates to impl anyway, but making it anunsafe trait
at least captures the UB potential.Additionally this adds more debug checks to
check_slice_length
to ensure that if there is a length mismatch, it's at least caught in debug builds.