Doc: MaybeUninit::assume_init_read Safety: warn on thread safety
#148398
+39
−0
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.
Fixes #148083.
Due to
impl<T: Sync> Sync for MaybeUninit<T>,MaybeUninit::assume_init_readis prone to the illegal use transferring ownership of!Send + Syncvalue across threads. This PR adds a warning on this thread safety problem to the method's Safety section. This PR also adds two code examples related to this problem.On the bad case code example: I wish I could use something better than
MutexGuard<'_, u32>, because I wasn't able to produce Miri-detectable UB.core::sync::Exclusive<&Cell<u32>>would be nice, but it's unstable.