Skip to content

Commit cee162f

Browse files
add MaybeDangling to core
Co-authored-by: Ralf Jung <post@ralfj.de>
1 parent 83e49b7 commit cee162f

File tree

2 files changed

+106
-0
lines changed

2 files changed

+106
-0
lines changed
Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
#![unstable(feature = "maybe_dangling", issue = "118166")]
2+
3+
use crate::{mem, ptr};
4+
5+
/// Allows wrapped [references] and [boxes] to dangle.
6+
///
7+
/// That is, if a reference (or a `Box`) is wrapped in `MaybeDangling` (including when in a
8+
/// (nested) field of a compound type wrapped in `MaybeDangling`), it does not have to follow
9+
/// pointer aliasing rules or be dereferenceable.
10+
///
11+
/// This can be useful when the value can become dangling while the function holding it is still
12+
/// executing (particularly in concurrent code). As a somewhat absurd example, consider this code:
13+
///
14+
/// ```rust,no_run
15+
/// #![feature(box_as_ptr)]
16+
/// # use std::alloc::{dealloc, Layout};
17+
/// # use std::mem;
18+
///
19+
/// let mut boxed = Box::new(0_u32);
20+
/// let ptr = Box::as_mut_ptr(&mut boxed);
21+
///
22+
/// // Safety: the pointer comes from a box and thus was allocated before; `box` is not used afterwards
23+
/// unsafe { dealloc(ptr.cast(), Layout::new::<u32>()) };
24+
///
25+
/// mem::forget(boxed); // <-- this is UB!
26+
/// ```
27+
///
28+
/// Even though the `Box`e's destructor is not run (and thus we don't have a double free bug), this
29+
/// code is still UB. This is because when moving `boxed` into `forget`, its validity invariants
30+
/// are asserted, causing UB since the `Box` is dangling.
31+
///
32+
/// To fix this we could use `MaybeDangling`:
33+
///
34+
/// ```rust
35+
/// #![feature(maybe_dangling, box_as_ptr)]
36+
/// # use std::alloc::{dealloc, Layout};
37+
/// # use std::mem::{self, MaybeDangling};
38+
///
39+
/// let mut boxed = MaybeDangling::new(Box::new(0_u32));
40+
/// let ptr = Box::as_mut_ptr(boxed.as_mut());
41+
///
42+
/// // Safety: the pointer comes from a box and thus was allocated before; `box` is not used afterwards
43+
/// unsafe { dealloc(ptr.cast(), Layout::new::<u32>()) };
44+
///
45+
/// mem::forget(boxed); // <-- this is OK!
46+
/// ```
47+
///
48+
/// Note that the bit pattern must still be valid for the wrapped type. That is, [references]
49+
/// (and [boxes]) still must be aligned and non-null.
50+
///
51+
/// Additionally note that safe code can still assume that the inner value in a `MaybeDangling` is
52+
/// **not** dangling -- functions like [`as_ref`] and [`into_inner`] are safe. It is not sound to
53+
/// return a dangling reference in a `MaybeDangling` to safe code. However, it *is* sound
54+
/// to hold such values internally inside your code -- and there's no way to do that without
55+
/// this type.
56+
///
57+
/// [references]: prim@reference
58+
/// [boxes]: ../../std/boxed/struct.Box.html
59+
/// [`into_inner`]: MaybeDangling::into_inner
60+
/// [`as_ref`]: MaybeDangling::as_ref
61+
#[repr(transparent)]
62+
#[rustc_pub_transparent]
63+
#[derive(Debug, Copy, Clone, Default)]
64+
pub struct MaybeDangling<P: ?Sized>(P);
65+
66+
impl<P: ?Sized> MaybeDangling<P> {
67+
/// Wraps a value in a `MaybeDangling`, allowing it to dangle.
68+
pub const fn new(x: P) -> Self
69+
where
70+
P: Sized,
71+
{
72+
MaybeDangling(x)
73+
}
74+
75+
/// Returns a reference to the inner value.
76+
///
77+
/// Note that this is UB if the inner value is currently dangling.
78+
pub const fn as_ref(&self) -> &P {
79+
&self.0
80+
}
81+
82+
/// Returns a mutable reference to the inner value.
83+
///
84+
/// Note that this is UB if the inner value is currently dangling.
85+
pub const fn as_mut(&mut self) -> &mut P {
86+
&mut self.0
87+
}
88+
89+
/// Extracts the value from the `MaybeDangling` container.
90+
///
91+
/// Note that this is UB if the inner value is currently dangling.
92+
pub const fn into_inner(self) -> P
93+
where
94+
P: Sized,
95+
{
96+
// FIXME: replace this with `self.0` when const checker can figure out that `self` isn't actually dropped
97+
// SAFETY: this is equivalent to `self.0`
98+
let x = unsafe { ptr::read(&self.0) };
99+
mem::forget(self);
100+
x
101+
}
102+
}

library/core/src/mem/mod.rs

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,10 @@ mod maybe_uninit;
1919
#[stable(feature = "maybe_uninit", since = "1.36.0")]
2020
pub use maybe_uninit::MaybeUninit;
2121

22+
mod maybe_dangling;
23+
#[unstable(feature = "maybe_dangling", issue = "118166")]
24+
pub use maybe_dangling::MaybeDangling;
25+
2226
mod transmutability;
2327
#[unstable(feature = "transmutability", issue = "99571")]
2428
pub use transmutability::{Assume, TransmuteFrom};

0 commit comments

Comments
 (0)