Skip to content

fix mem::uninitialized deprecation schedule #396

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

Merged
merged 1 commit into from
Jul 15, 2019
Merged

fix mem::uninitialized deprecation schedule #396

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion posts/2019-07-04-Rust-1.36.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ The Rust compiler will understand that it should not assume that a [`MaybeUninit
Therefore, you can do gradual initialization more safely and eventually use `.assume_init()`
once you are certain that `maybe_t: MaybeUninit<T>` contains an initialized `T`.

As [`MaybeUninit<T>`] is the safer alternative, starting with Rust 1.38,
As [`MaybeUninit<T>`] is the safer alternative, starting with Rust 1.39,
the function [`mem::uninitialized`] will be deprecated.

To find out more about uninitialized memory, [`mem::uninitialized`],
Expand Down