-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
Add MaybeDangling to core
#149775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
WaffleLapkin
wants to merge
4
commits into
rust-lang:main
Choose a base branch
from
WaffleLapkin:core-mem-maybe-dangling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+392
−200
Open
Add MaybeDangling to core
#149775
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,113 @@ | ||
| #![unstable(feature = "maybe_dangling", issue = "118166")] | ||
|
|
||
| use crate::{mem, ptr}; | ||
|
|
||
| /// Allows wrapped [references] and [boxes] to dangle. | ||
| /// | ||
| /// <section class="warning"> | ||
| /// This type is not properly implemented yet, and the documentation below is thus not accurate. | ||
| /// </section> | ||
| /// | ||
| /// 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: | ||
| /// | ||
| /// ```rust,no_run | ||
| /// #![feature(box_as_ptr)] | ||
| /// # use std::alloc::{dealloc, Layout}; | ||
| /// # use std::mem; | ||
| /// | ||
| /// 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`e'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`: | ||
| /// | ||
| /// ```rust | ||
| /// #![feature(maybe_dangling, box_as_ptr)] | ||
| /// # use std::alloc::{dealloc, Layout}; | ||
| /// # use std::mem::{self, MaybeDangling}; | ||
| /// | ||
| /// 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 | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How do we deal with the implicit Drop for the inner type? Should callers who place e.g. a dangling Box inside just be careful to call forget rather than letting it Drop? |
||
| /// 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. | ||
| /// | ||
| /// [references]: prim@reference | ||
| /// [boxes]: ../../std/boxed/struct.Box.html | ||
| /// [`into_inner`]: MaybeDangling::into_inner | ||
| /// [`as_ref`]: MaybeDangling::as_ref | ||
| /// [`ManuallyDrop`]: crate::mem::ManuallyDrop | ||
| #[repr(transparent)] | ||
| #[rustc_pub_transparent] | ||
| #[derive(Debug, Copy, Clone, Default)] | ||
| pub struct MaybeDangling<P: ?Sized>(P); | ||
|
|
||
| impl<P: ?Sized> MaybeDangling<P> { | ||
| /// Wraps a value in a `MaybeDangling`, allowing it to dangle. | ||
| pub const fn new(x: P) -> Self | ||
| where | ||
| P: Sized, | ||
| { | ||
| MaybeDangling(x) | ||
| } | ||
|
|
||
| /// Returns a reference to the inner value. | ||
| /// | ||
| /// Note that this is UB if the inner value is currently dangling. | ||
| pub const fn as_ref(&self) -> &P { | ||
| &self.0 | ||
| } | ||
|
|
||
| /// Returns a mutable reference to the inner value. | ||
| /// | ||
| /// Note that this is UB if the inner value is currently dangling. | ||
| pub const fn as_mut(&mut self) -> &mut P { | ||
| &mut self.0 | ||
| } | ||
|
|
||
| /// Extracts the value from the `MaybeDangling` container. | ||
| /// | ||
| /// Note that this is UB if the inner value is currently dangling. | ||
| pub const fn into_inner(self) -> P | ||
| where | ||
| P: Sized, | ||
| { | ||
| // FIXME: replace this with `self.0` when const checker can figure out that `self` isn't actually dropped | ||
| // SAFETY: this is equivalent to `self.0` | ||
| let x = unsafe { ptr::read(&self.0) }; | ||
| mem::forget(self); | ||
| x | ||
| } | ||
| } | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 2 additions & 2 deletions
4
src/tools/miri/tests/pass/stacked_borrows/stack-printing.stdout
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| 0..1: [ SharedReadWrite<TAG> ] | ||
| 0..1: [ SharedReadWrite<TAG> ] | ||
| 0..1: [ SharedReadWrite<TAG> ] | ||
| 0..1: [ SharedReadWrite<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> ] | ||
| 0..1: [ SharedReadWrite<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> SharedReadOnly<TAG> ] | ||
| 0..1: [ SharedReadWrite<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> Unique<TAG> ] | ||
| 0..1: [ SharedReadWrite<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> Disabled<TAG> SharedReadOnly<TAG> ] | ||
| 0..1: [ unknown-bottom(..<TAG>) ] |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a "Not yet actually implemented" or perhaps make
maybe_danglingan incomplete lang feature? I worry a bit that as of this PR, from what I can tell, this is UB to use as documented, right? Since the compiler bits aren't there yet.