Use MaybeUninit instead of ManuallyDrop to inhibit the validity invariant of the storage type #3
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 fixes the tests added in the first commit, which failed previously:
Box<_>
contains a pointer that is known not to be null, soOption<Box<_>>
can be stored on a single pointer with null representingNone
. This also works for structs that contain aBox
field, even withinManuallyDrop
, so writing zero to that memory location is incorrect. WithMaybeUninit
however, it is correct for any byte of the memory representation to be zero (or not initialized) so the enum layout optimization does not use niches found withinMaybeUninit
.Also some less important drive-by changes in the latter two commits, let me know if you’d prefer having them separately or not having them.