Change BufMut methods that expose maybe-uninitialized bytes #305
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.
BufMut::bytes_mut
is now&mut [MaybeUninit<u8>]
.BufMut::bytes_vectored_mut
is now&mut [bytes::buf::IoSliceMut]
.bytes::buf::IoSliceMut
is arepr(transparent)
wrapper around anstd::io::IoSliceMut
, but does not expose the inner bytes with a safeAPI, since they might be uninitialized.
BufMut::bytesMut
andBufMut::bytes_vectored_mut
are no longerunsafe fn
, since the types encapsulate the unsafety instead.