Enum rustc_middle::mir::BorrowKind [−][src]
pub enum BorrowKind {
Shared,
Shallow,
Unique,
Mut {
allow_two_phase_borrow: bool,
},
}
Variants
Data must be immutable and is aliasable.
The immediately borrowed place must be immutable, but projections from
it don’t need to be. For example, a shallow borrow of a.b
doesn’t
conflict with a mutable borrow of a.b.c
.
This is used when lowering matches: when matching on a place we want to ensure that place have the same value from the start of the match until an arm is selected. This prevents this code from compiling:
let mut x = &Some(0);
match *x {
None => (),
Some(_) if { x = &None; false } => (),
Some(_) => (),
}
This can’t be a shared borrow because mutably borrowing (*x as Some).0
should not prevent if let None = x { ... }
, for example, because the
mutating (*x as Some).0
can’t affect the discriminant of x
.
We can also report errors with this kind of borrow differently.
Data must be immutable but not aliasable. This kind of borrow cannot currently be expressed by the user and is used only in implicit closure bindings. It is needed when the closure is borrowing or mutating a mutable referent, e.g.:
let x: &mut isize = ...;
let y = || *x += 5;
If we were to try to translate this closure into a more explicit form, we’d encounter an error with the code as written:
struct Env { x: & &mut isize }
let x: &mut isize = ...;
let y = (&mut Env { &x }, fn_ptr); // Closure is pair of env and fn
fn fn_ptr(env: &mut Env) { **env.x += 5; }
This is then illegal because you cannot mutate an &mut
found
in an aliasable location. To solve, you’d have to translate with
an &mut
borrow:
struct Env { x: &mut &mut isize }
let x: &mut isize = ...;
let y = (&mut Env { &mut x }, fn_ptr); // changed from &x to &mut x
fn fn_ptr(env: &mut Env) { **env.x += 5; }
Now the assignment to **env.x
is legal, but creating a
mutable pointer to x
is not because x
is not mutable. We
could fix this by declaring x
as let mut x
. This is ok in
user code, if awkward, but extra weird for closures, since the
borrow is hidden.
So we introduce a “unique imm” borrow – the referent is immutable, but not aliasable. This solves the problem. For simplicity, we don’t give users the way to express this borrow, it’s just used when translating closures.
Data is mutable and not aliasable.
Fields of Mut
allow_two_phase_borrow: bool
true
if this borrow arose from method-call auto-ref
(i.e., adjustment::Adjust::Borrow
).
Implementations
Trait Implementations
This method tests for self
and other
values to be equal, and is used
by ==
. Read more
This method tests for !=
.
This method returns an ordering between self
and other
values if one exists. Read more
This method tests less than (for self
and other
) and is used by the <
operator. Read more
This method tests less than or equal to (for self
and other
) and is used by the <=
operator. Read more
This method tests greater than (for self
and other
) and is used by the >
operator. Read more
Auto Trait Implementations
impl RefUnwindSafe for BorrowKind
impl Send for BorrowKind
impl Sync for BorrowKind
impl Unpin for BorrowKind
impl UnwindSafe for BorrowKind
Blanket Implementations
Mutably borrows from an owned value. Read more
impl<Ctxt, T> DepNodeParams<Ctxt> for T where
Ctxt: DepContext,
T: for<'a> HashStable<StableHashingContext<'a>> + Debug,
impl<Ctxt, T> DepNodeParams<Ctxt> for T where
Ctxt: DepContext,
T: for<'a> HashStable<StableHashingContext<'a>> + Debug,
This method turns the parameters of a DepNodeConstructor into an opaque Fingerprint to be used in DepNode. Not all DepNodeParams support being turned into a Fingerprint (they don’t need to if the corresponding DepNode is anonymous). Read more
This method tries to recover the query key from the given DepNode
,
something which is needed when forcing DepNode
s during red-green
evaluation. The query system will only call this method if
fingerprint_style()
is not FingerprintStyle::Opaque
.
It is always valid to return None
here, in which case incremental
compilation will treat the query as having changed instead of forcing it. Read more
Layout
Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...)
attributes. Please see the Rust Reference’s “Type Layout” chapter for details on type layout guarantees.
Size: 1 byte
Size for each variant:
Shared
: 0 bytesShallow
: 0 bytesUnique
: 0 bytesMut
: 1 byte