| Crates.io | maybe-dangling |
| lib.rs | maybe-dangling |
| version | 0.1.1 |
| created_at | 2023-06-20 10:55:21.995114+00 |
| updated_at | 2023-12-10 10:12:50.43262+00 |
| description | `ManuallyDrop |
| homepage | |
| repository | https://github.com/danielhenrymantilla/maybe-dangling.rs |
| max_upload_size | |
| id | 894969 |
| size | 48,302 |
::maybe-danglingManuallyDrop<T> and MaybeDangling<T> semantics in stable Rust as per https://github.com/rust-lang/rfcs/pull/3336
This crates offers two types, ManuallyDrop<T>, and MaybeDangling<T>, which do not carry
aliasing/dereferenceable-ity properties w.r.t. the
T they each contain, which means they are allowed to:
T = &'expired …,::core::mem::forget()),The RFC that shall eventually and ultimately supersede this very crate: https://github.com/rust-lang/rfcs/pull/3336
The miri PR implementing the check against this: https://github.com/rust-lang/miri/pull/2985
The soundness problem of ::ouroboros stemming from not using this: https://github.com/joshua-maros/ouroboros/issues/88
The soundness problem of ::yoke stemming from not using this: https://github.com/unicode-org/icu4x/issues/3696
An URLO thread on the topic, and a post exposing the intention to write this very crate