From 2ab1783f2d2c862c3557fd8e1cf3cfe9396fc505 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Sun, 15 Sep 2019 14:11:23 +0200 Subject: [PATCH] remove a pointless remark --- src/unchecked-uninit.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/unchecked-uninit.md b/src/unchecked-uninit.md index 6636050..ca24498 100644 --- a/src/unchecked-uninit.md +++ b/src/unchecked-uninit.md @@ -110,8 +110,7 @@ arbitrary locations of memory can break things are basically uncountable! It's worth noting that you don't need to worry about `ptr::write`-style shenanigans with types which don't implement `Drop` or contain `Drop` types, because Rust knows not to try to drop them. This is what we relied on in the -above example. Similarly you should be able to assign to fields of partially -initialized structs directly if those fields don't contain any `Drop` types. +above example. However when working with uninitialized memory you need to be ever-vigilant for Rust trying to drop values you make like this before they're fully initialized.