Struct rustc_mir_dataflow::impls::borrowed_locals::MaybeBorrowedLocals[][src]

pub struct MaybeBorrowedLocals<K = AnyBorrow> {
    kind: K,
    ignore_borrow_on_drop: bool,
}
Expand description

A dataflow analysis that tracks whether a pointer or reference could possibly exist that points to a given local.

The K parameter determines what kind of borrows are tracked. By default, MaybeBorrowedLocals looks for any borrow of a local. If you are only interested in borrows that might allow mutation, use the MaybeMutBorrowedLocals type alias instead.

At present, this is used as a very limited form of alias analysis. For example, MaybeBorrowedLocals is used to compute which locals are live during a yield expression for immovable generators. MaybeMutBorrowedLocals is used during const checking to prove that a local has not been mutated via indirect assignment (e.g., *p = 42), the side-effects of a function call or inline assembly.

Fields

kind: Kignore_borrow_on_drop: bool

Implementations

A dataflow analysis that records whether a pointer or reference exists that may alias the given local.

A dataflow analysis that records whether a pointer or reference exists that may mutably alias the given local.

This includes &mut and pointers derived from an &mut, as well as shared borrows of types with interior mutability.

During dataflow analysis, ignore the borrow that may occur when a place is dropped.

Drop terminators may call custom drop glue (Drop::drop), which takes &mut self as a parameter. In the general case, a drop impl could launder that reference into the surrounding environment through a raw pointer, thus creating a valid *mut pointing to the dropped local. We are not yet willing to declare this particular case UB, so we must treat all dropped locals as mutably borrowed for now. See discussion on #61069.

In some contexts, we know that this borrow will never occur. For example, during const-eval, custom drop glue cannot be run. Code that calls this should document the assumptions that justify ignoring Drop terminators in this way.

Trait Implementations

The type that holds the dataflow state at any given point in the program.

A descriptive name for this analysis. Used only for debugging. Read more

The initial value of the dataflow state upon entry to each basic block.

Mutates the initial value of the dataflow state upon entry to the START_BLOCK. Read more

The direction of this analysis. Either Forward or Backward.

See Analysis::apply_statement_effect.

See Analysis::apply_terminator_effect.

See Analysis::apply_call_return_effect.

See Analysis::apply_before_statement_effect.

See Analysis::apply_before_terminator_effect.

See Analysis::apply_yield_resume_effect.

See Analysis::apply_switch_int_edge_effects.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Performs the conversion.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.

Layout

Note: Unable to compute type layout, possibly due to this type having generic parameters. Layout can only be computed for concrete, fully-instantiated types.