drop_in_place is stable now, don't #![feature] it in the nomicon and a test

It was stable since Rust 1.8.
pull/10/head
est31 8 years ago committed by Manish Goregaokar
parent e8afb6db19
commit 46f632d85f

@ -26,7 +26,7 @@ this is totally fine.
For instance, a custom implementation of `Box` might write `Drop` like this:
```rust
#![feature(alloc, heap_api, drop_in_place, unique)]
#![feature(alloc, heap_api, unique)]
extern crate alloc;
@ -57,7 +57,7 @@ use-after-free the `ptr` because when drop exits, it becomes inaccessible.
However this wouldn't work:
```rust
#![feature(alloc, heap_api, drop_in_place, unique)]
#![feature(alloc, heap_api, unique)]
extern crate alloc;
@ -135,7 +135,7 @@ The classic safe solution to overriding recursive drop and allowing moving out
of Self during `drop` is to use an Option:
```rust
#![feature(alloc, heap_api, drop_in_place, unique)]
#![feature(alloc, heap_api, unique)]
extern crate alloc;

Loading…
Cancel
Save