Fix possible undefined behavior in primitive list as_slice #496
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.
At least on my machine, calling
.as_slice()
on an empty primitive list with elements u16 or larger in Rust nightly in debug mode results in a panic like this:This is because
ListReader::into_raw_bytes
andListBuilder::as_raw_bytes
return an empty&[u8]
when the list is empty, which has a pointer value of 1 in this version of Rust.The documentation for
std::slice::from_raw_parts
notes:This PR adds a check to avoid creating an invalid empty slice and and adds some test cases for empty primitive lists of larger types.