Patrick Walton dcbf4ec2a1 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]		2014-06-20 14:24:31 -07:00
..
auxiliary	librustc: Put #[unsafe_destructor] behind a feature gate.	2014-06-20 14:24:31 -07:00
bench	librustc: Put #[unsafe_destructor] behind a feature gate.	2014-06-20 14:24:31 -07:00
codegen	Add pub to all the codegen tests	2013-10-10 06:00:51 -07:00
compile-fail	librustc: Put #[unsafe_destructor] behind a feature gate.	2014-06-20 14:24:31 -07:00
compile-fail-fulldeps	rustc: reduce redundant resolve errors.	2014-06-18 01:19:22 +01:00
debuginfo	debuginfo: Add test case for issue 14411.	2014-06-18 17:02:02 -07:00
pretty	rustc: Obsolete the @ syntax entirely	2014-06-14 10:45:37 -07:00
run-fail	librustc: Put #[unsafe_destructor] behind a feature gate.	2014-06-20 14:24:31 -07:00
run-make	auto merge of #15006 : alexcrichton/rust/fix-nightly, r=brson	2014-06-18 22:41:40 +00:00
run-pass	librustc: Put #[unsafe_destructor] behind a feature gate.	2014-06-20 14:24:31 -07:00
run-pass-fulldeps	rustc: Obsolete the @ syntax entirely	2014-06-14 10:45:37 -07:00