#[repr(transparent)]pub struct MaybeDangling<P>(P)
where
P: ?Sized;maybe_dangling #118166)Expand description
Allows wrapped references and boxes to dangle.
That is, if a reference (or a Box) is wrapped in MaybeDangling (including when in a
(nested) field of a compound type wrapped in MaybeDangling), it does not have to follow
pointer aliasing rules or be dereferenceable.
This can be useful when the value can become dangling while the function holding it is still executing (particularly in concurrent code). As a somewhat absurd example, consider this code:
#![feature(box_as_ptr)]
let mut boxed = Box::new(0_u32);
let ptr = Box::as_mut_ptr(&mut boxed);
// Safety: the pointer comes from a box and thus was allocated before; `box` is not used afterwards
unsafe { dealloc(ptr.cast(), Layout::new::<u32>()) };
mem::forget(boxed); // <-- this is UB!Even though the Box’s destructor is not run (and thus we don’t have a double free bug), this
code is still UB. This is because when moving boxed into forget, its validity invariants
are asserted, causing UB since the Box is dangling. The safety comment is as such wrong, as
moving the boxed variable as part of the forget call is a use.
To fix this we could use MaybeDangling:
#![feature(maybe_dangling, box_as_ptr)]
let mut boxed = MaybeDangling::new(Box::new(0_u32));
let ptr = Box::as_mut_ptr(boxed.as_mut());
// Safety: the pointer comes from a box and thus was allocated before; `box` is not used afterwards
unsafe { dealloc(ptr.cast(), Layout::new::<u32>()) };
mem::forget(boxed); // <-- this is OK!Note that the bit pattern must still be valid for the wrapped type. That is, references (and boxes) still must be aligned and non-null.
Additionally note that safe code can still assume that the inner value in a MaybeDangling is
not dangling – functions like as_ref and into_inner are safe. It is not sound to
return a dangling reference in a MaybeDangling to safe code. However, it is sound
to hold such values internally inside your code – and there’s no way to do that without
this type. Note that other types can use this type and thus get the same effect; in particular,
ManuallyDrop will use MaybeDangling.
Note that MaybeDangling doesn’t prevent drops from being run, which can lead to UB if the
drop observes a dangling value. If you need to prevent drops from being run use ManuallyDrop
instead.
Tuple Fields§
§0: Pmaybe_dangling #118166)Implementations§
Source§impl<P> MaybeDangling<P>where
P: ?Sized,
impl<P> MaybeDangling<P>where
P: ?Sized,
Sourcepub const fn new(x: P) -> MaybeDangling<P>
🔬This is a nightly-only experimental API. (maybe_dangling #118166)
pub const fn new(x: P) -> MaybeDangling<P>
maybe_dangling #118166)Wraps a value in a MaybeDangling, allowing it to dangle.
Sourcepub const fn as_ref(&self) -> &P
🔬This is a nightly-only experimental API. (maybe_dangling #118166)
pub const fn as_ref(&self) -> &P
maybe_dangling #118166)Returns a reference to the inner value.
Note that this is UB if the inner value is currently dangling.
Sourcepub const fn as_mut(&mut self) -> &mut P
🔬This is a nightly-only experimental API. (maybe_dangling #118166)
pub const fn as_mut(&mut self) -> &mut P
maybe_dangling #118166)Returns a mutable reference to the inner value.
Note that this is UB if the inner value is currently dangling.
Sourcepub const fn into_inner(self) -> P
🔬This is a nightly-only experimental API. (maybe_dangling #118166)
pub const fn into_inner(self) -> P
maybe_dangling #118166)Extracts the value from the MaybeDangling container.
Note that this is UB if the inner value is currently dangling.
Trait Implementations§
Source§impl<P> Clone for MaybeDangling<P>
impl<P> Clone for MaybeDangling<P>
Source§fn clone(&self) -> MaybeDangling<P>
fn clone(&self) -> MaybeDangling<P>
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl<P> Debug for MaybeDangling<P>
impl<P> Debug for MaybeDangling<P>
Source§impl<P> Default for MaybeDangling<P>
impl<P> Default for MaybeDangling<P>
Source§fn default() -> MaybeDangling<P>
fn default() -> MaybeDangling<P>
impl<P> Copy for MaybeDangling<P>
Auto Trait Implementations§
impl<P> Freeze for MaybeDangling<P>
impl<P> RefUnwindSafe for MaybeDangling<P>where
P: RefUnwindSafe + ?Sized,
impl<P> Send for MaybeDangling<P>
impl<P> Sync for MaybeDangling<P>
impl<P> Unpin for MaybeDangling<P>
impl<P> UnsafeUnpin for MaybeDangling<P>where
P: UnsafeUnpin + ?Sized,
impl<P> UnwindSafe for MaybeDangling<P>where
P: UnwindSafe + ?Sized,
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> SizedTypeProperties for T
impl<T> SizedTypeProperties for T
Source§#[doc(hidden)]const SIZE: usize = _
#[doc(hidden)]const SIZE: usize = _
sized_type_properties)Source§#[doc(hidden)]const ALIGN: usize = _
#[doc(hidden)]const ALIGN: usize = _
sized_type_properties)Source§#[doc(hidden)]const ALIGNMENT: Alignment = _
#[doc(hidden)]const ALIGNMENT: Alignment = _
ptr_alignment_type #102070)Source§#[doc(hidden)]const IS_ZST: bool = _
#[doc(hidden)]const IS_ZST: bool = _
sized_type_properties)Source§#[doc(hidden)]const LAYOUT: Layout = _
#[doc(hidden)]const LAYOUT: Layout = _
sized_type_properties)Source§#[doc(hidden)]const MAX_SLICE_LEN: usize = _
#[doc(hidden)]const MAX_SLICE_LEN: usize = _
sized_type_properties)[Self]. Read more