Skip to content

aliasing model summary: fix incorrect definition of liveness #2394

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.

Sign up for GitHub

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
RalfJung wants to merge 1 commit into
base: master
Choose a base branch
from
Open

aliasing model summary: fix incorrect definition of liveness #2394

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/behavior-considered-undefined.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ r[undefined.alias]
* For references, the liveness duration is upper-bounded by the syntactic lifetime assigned by the borrow checker; it cannot be live any *longer* than that lifetime.
* Each time a reference or box is dereferenced or reborrowed, it is considered live.
* Each time a reference or box is passed to or returned from a function, it is considered live.
* When a reference (but not a `Box`!) is passed to a function, it is live at least as long as that function call, again except if the `&T` contains an [`UnsafeCell<U>`].
* When a reference (but not a `Box`!) is passed to a function, it is live at least as long as that function call. As an exception, for shared references `&T`, the reference does not have to remain live for data inside an [`UnsafeCell<U>`].

All this also applies when values of these types are passed in a (nested) field of a compound type, but not behind pointer indirections.

Expand Down
Loading