Auto merge of #39304 - jrmuizel:drop-flags, r=steveklabnik

Remove obsolete documentation about drop-flags

1 files changed, 2 insertions, 14 deletions

diff --git a/src/doc/nomicon/src/drop-flags.md b/src/doc/nomicon/src/drop-flags.md
index 51fa9d0a3c0..e69264f281c 100644
--- a/src/doc/nomicon/src/drop-flags.md
+++ b/src/doc/nomicon/src/drop-flags.md
@@ -79,17 +79,5 @@ if condition {
 }
 ```
 
-As of Rust 1.0, the drop flags are actually not-so-secretly stashed in a hidden
-field of any type that implements Drop. Rust sets the drop flag by overwriting
-the entire value with a particular bit pattern. This is pretty obviously Not
-The Fastest and causes a bunch of trouble with optimizing code. It's legacy from
-a time when you could do much more complex conditional initialization.
-
-As such work is currently under way to move the flags out onto the stack frame
-where they more reasonably belong. Unfortunately, this work will take some time
-as it requires fairly substantial changes to the compiler.
-
-Regardless, Rust programs don't need to worry about uninitialized values on
-the stack for correctness. Although they might care for performance. Thankfully,
-Rust makes it easy to take control here! Uninitialized values are there, and
-you can work with them in Safe Rust, but you're never in danger.
+The drop flags are tracked on the stack and no longer stashed in types that
+implement drop.