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/librustrt/lib.rs | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'src/librustrt') diff --git a/src/librustrt/lib.rs b/src/librustrt/lib.rs index c461dccceff..f5521886f52 100644 --- a/src/librustrt/lib.rs +++ b/src/librustrt/lib.rs @@ -15,10 +15,12 @@ #![doc(html_logo_url = "http://www.rust-lang.org/logos/rust-logo-128x128-blk-v2.png", html_favicon_url = "http://www.rust-lang.org/favicon.ico", html_root_url = "http://doc.rust-lang.org/")] -#![feature(macro_rules, phase, globs, thread_local, managed_boxes, asm, - linkage)] + +#![feature(macro_rules, phase, globs, thread_local, managed_boxes, asm)] +#![feature(linkage, unsafe_destructor)] #![no_std] #![experimental] +#![allow(unknown_features)] // NOTE: remove after a stage0 snap #[phase(plugin, link)] extern crate core; extern crate alloc; -- cgit 1.4.1-3-g733a5