Don't call assume_init on Deferred's Data #779
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.
This situation can be observed by running
MIRIFLAGS="-Zmiri-check-number-validity" cargo miri test
incrossbeam/crossbeam-deque
:In the crossbeam-deque test suite, a
Deferred
was created from aFnOnce
which is smaller than theData
. This makes the call toMaybeUninit::assume_init()
immediate UB (the reference to it created upon call is probably UB too). The docs forMaybeUninit::assume_init()
say this:Since
Data
doesn't have aDrop
impl, we can just leave it in theMaybeUninit
wrapper. This removes all issues about type validity.