From 638f52765529ba174d0c5dde652c4ed4e6d881d4 Mon Sep 17 00:00:00 2001 From: Andrew Paseltiner Date: Sun, 4 Sep 2016 22:57:27 -0400 Subject: [PATCH] Remove mention of `unsafe_no_drop_flag` from Reference and Nomicon --- safe-unsafe-meaning.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/safe-unsafe-meaning.md b/safe-unsafe-meaning.md index c4f939a..adede0e 100644 --- a/safe-unsafe-meaning.md +++ b/safe-unsafe-meaning.md @@ -26,10 +26,6 @@ can therefore be trusted. You can use `unsafe` on a trait implementation to declare that the implementation of that trait has adhered to whatever contracts the trait's documentation requires. -There is also the `#[unsafe_no_drop_flag]` attribute, which exists for -historic reasons and is being phased out. See the section on [drop flags] -for details. - The standard library has a number of unsafe functions, including: * `slice::get_unchecked`, which performs unchecked indexing, allowing