From dcbf4ec2a1cfd9f521c96b9dab62a2d27ded1b24 Mon Sep 17 00:00:00 2001 From: Patrick Walton Date: Tue, 17 Jun 2014 16:00:04 -0700 Subject: librustc: Put `#[unsafe_destructor]` behind a feature gate. Closes #8142. This is not the semantics we want long-term. You can continue to use `#[unsafe_destructor]`, but you'll need to add `#![feature(unsafe_destructor)]` to the crate attributes. [breaking-change] --- src/doc/rust.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'src/doc/rust.md') diff --git a/src/doc/rust.md b/src/doc/rust.md index 7e5e5b2e67a..ca5ecc191cc 100644 --- a/src/doc/rust.md +++ b/src/doc/rust.md @@ -1940,12 +1940,13 @@ interpreted: enum representation in C is undefined, and this may be incorrect when the C code is compiled with certain flags. - `simd` - on certain tuple structs, derive the arithmetic operators, which - lower to the target's SIMD instructions, if any. + lower to the target's SIMD instructions, if any; the `simd` feature gate + is necessary to use this attribute. - `static_assert` - on statics whose type is `bool`, terminates compilation with an error if it is not initialized to `true`. - `unsafe_destructor` - allow implementations of the "drop" language item where the type it is implemented for does not implement the "send" language - item. + item; the `unsafe_destructor` feature gate is needed to use this attribute - `unsafe_no_drop_flag` - on structs, remove the flag that prevents destructors from being run twice. Destructors might be run multiple times on the same object with this attribute. -- cgit 1.4.1-3-g733a5