Struct PoloniusOutOfScopePrecomputer

struct PoloniusOutOfScopePrecomputer<'a, 'tcx> {
    visited: BitSet<BasicBlock>,
    visit_stack: Vec<BasicBlock>,
    body: &'a Body<'tcx>,
    regioncx: &'a RegionInferenceContext<'tcx>,
    loans_out_of_scope_at_location: FxIndexMap<Location, Vec<BorrowIndex>>,
}

Fields

visited: BitSet<BasicBlock>

visit_stack: Vec<BasicBlock>

body: &'a Body<'tcx>

regioncx: &'a RegionInferenceContext<'tcx>

loans_out_of_scope_at_location: FxIndexMap<Location, Vec<BorrowIndex>>

Implementations

impl<'a, 'tcx> PoloniusOutOfScopePrecomputer<'a, 'tcx>

fn new(body: &'a Body<'tcx>, regioncx: &'a RegionInferenceContext<'tcx>) -> Self

impl<'tcx> PoloniusOutOfScopePrecomputer<'_, 'tcx>

fn precompute_loans_out_of_scope( &mut self, loan_idx: BorrowIndex, issuing_region: RegionVid, loan_issued_at: Location, )

Loans are in scope while they are live: whether they are contained within any live region. In the location-insensitive analysis, a loan will be contained in a region if the issuing region can reach it in the subset graph. So this is a reachability problem.

fn loan_kill_location( &self, loan_idx: BorrowIndex, loan_issued_at: Location, block: BasicBlock, start: usize, end: usize, ) -> Option<Location>

Returns the lowest statement in start..=end, where the loan goes out of scope, if any. This is the statement where the issuing region can’t reach any of the regions that are live at this point.

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: 128 bytes