Allow uses of #[unsafe_destructor_blind_to_params]. Should be ported to #[may_dangle].

See #34761.

Author: pnkfelix

src/test/ui/run-pass/issues/issue28498-ugeh-ex1.rs

@@ -9,6 +9,8 @@
 // except according to those terms.
 
 // run-pass
+#![allow(deprecated)] // FIXME: switch to `#[may_dangle]` below.
+
 // Example taken from RFC 1238 text
 
 // https://github.com/rust-lang/rfcs/blob/master/text/1238-nonparametric-dropck.md

src/test/ui/run-pass/issues/issue28498-ugeh-with-lifetime-param.rs

@@ -9,6 +9,8 @@
 // except according to those terms.
 
 // run-pass
+#![allow(deprecated)] // FIXME: switch to `#[may_dangle]` below.
+
 // Demonstrate the use of the unguarded escape hatch with a lifetime param
 // to assert that destructor will not access any dead data.
 //

src/test/ui/run-pass/issues/issue28498-ugeh-with-passed-to-fn.rs

@@ -9,6 +9,8 @@
 // except according to those terms.
 
 // run-pass
+#![allow(deprecated)] // FIXME: switch to `#[may_dangle]` below.
+
 // Demonstrate the use of the unguarded escape hatch with a type param in negative position
 // to assert that destructor will not access any dead data.
 //

src/test/ui/run-pass/issues/issue28498-ugeh-with-trait-bound.rs

@@ -9,6 +9,8 @@
 // except according to those terms.
 
 // run-pass
+#![allow(deprecated)] // FIXME: switch to `#[may_dangle]` below.
+
 // Demonstrate the use of the unguarded escape hatch with a trait bound
 // to assert that destructor will not access any dead data.
 //