Fix into_owned
String
not having enough provenance
#47
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.
Calling
.as_mut_ptr
on aString
actually goes through&mut str
, which shrinks the provenance of the pointer to only contain the initialized bytes. This caused issues when a reconstructedString
tried to write to the uninitialized part of it. The fix is to go throughVec::<u8>::as_mut_ptr
, which gives provenance for the entire allocation.