From 6c6ebda37c832e2d92526495387f9dade8409f68 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Sat, 13 Jul 2019 09:36:53 +0200 Subject: [PATCH] fix mem::uninitialized deprecation schedule --- posts/2019-07-04-Rust-1.36.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2019-07-04-Rust-1.36.0.md b/posts/2019-07-04-Rust-1.36.0.md index f987bf57e..35ed5b8e4 100644 --- a/posts/2019-07-04-Rust-1.36.0.md +++ b/posts/2019-07-04-Rust-1.36.0.md @@ -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` contains an initialized `T`. -As [`MaybeUninit`] is the safer alternative, starting with Rust 1.38, +As [`MaybeUninit`] 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`],