Skip to content

core: clarify MaybeUninit::assume_init UB for uninitialized integers #153253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
laddery-a wants to merge 2 commits into from
Closed

core: clarify MaybeUninit::assume_init UB for uninitialized integers #153253

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e30555b
core: clarify assume_init UB for uninitialized integers
laddery-a Mar 1, 2026
3f0ac2c
core: avoid POD wording in MaybeUninit::assume_init docs
laddery-a Mar 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions library/core/src/mem/maybe_uninit.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -658,8 +658,8 @@ impl<T> MaybeUninit<T> {
///
/// It is up to the caller to guarantee that the `MaybeUninit<T>` really is in an initialized
/// state. Calling this when the content is not yet fully initialized causes immediate undefined
/// behavior. The [type-level documentation][inv] contains more information about
/// this initialization invariant.
/// behavior, even if `T` is an integer type. The [type-level documentation][inv] contains more
/// information about this initialization invariant.
///
/// [inv]: #initialization-invariant
///
Expand Down
Loading