Struct rustc_borrowck::type_check::liveness::trace::LivenessContext
source · [−]struct LivenessContext<'me, 'typeck, 'flow, 'tcx> {
typeck: &'me mut TypeChecker<'typeck, 'tcx>,
elements: &'me RegionValueElements,
body: &'me Body<'tcx>,
move_data: &'me MoveData<'tcx>,
drop_data: FxHashMap<Ty<'tcx>, DropData<'tcx>>,
flow_inits: &'me mut ResultsCursor<'flow, 'tcx, MaybeInitializedPlaces<'flow, 'tcx>>,
local_use_map: &'me LocalUseMap,
}Expand description
Contextual state for the type-liveness generator.
Fields
typeck: &'me mut TypeChecker<'typeck, 'tcx>Current type-checker, giving us our inference context etc.
elements: &'me RegionValueElementsDefines the PointIndex mapping
body: &'me Body<'tcx>MIR we are analyzing.
move_data: &'me MoveData<'tcx>Mapping to/from the various indices used for initialization tracking.
drop_data: FxHashMap<Ty<'tcx>, DropData<'tcx>>Cache for the results of dropck_outlives query.
flow_inits: &'me mut ResultsCursor<'flow, 'tcx, MaybeInitializedPlaces<'flow, 'tcx>>Results of dataflow tracking which variables (and paths) have been initialized.
local_use_map: &'me LocalUseMapIndex indicating where each variable is assigned, used, or dropped.
Implementations
Returns true if the local variable (or some part of it) is initialized at the current
cursor position. Callers should call one of the seek methods immediately before to point
the cursor to the desired location.
Returns true if the local variable (or some part of it) is initialized in
the terminator of block. We need to check this to determine if a
DROP of some local variable will have an effect – note that
drops, as they may unwind, are always terminators.
Returns true if the path mpi (or some part of it) is initialized at
the exit of block.
Warning: Does not account for the result of Call
instructions.
fn add_use_live_facts_for(
&mut self,
value: impl TypeFoldable<'tcx>,
live_at: &IntervalSet<PointIndex>
)
fn add_use_live_facts_for(
&mut self,
value: impl TypeFoldable<'tcx>,
live_at: &IntervalSet<PointIndex>
)
Stores the result that all regions in value are live for the
points live_at.
fn add_drop_live_facts_for(
&mut self,
dropped_local: Local,
dropped_ty: Ty<'tcx>,
drop_locations: &[Location],
live_at: &IntervalSet<PointIndex>
)
fn add_drop_live_facts_for(
&mut self,
dropped_local: Local,
dropped_ty: Ty<'tcx>,
drop_locations: &[Location],
live_at: &IntervalSet<PointIndex>
)
Some variable with type live_ty is “drop live” at location
– i.e., it may be dropped later. This means that some of
the regions in its type must be live at location. The
precise set will depend on the dropck constraints, and in
particular this takes #[may_dangle] into account.
fn make_all_regions_live(
elements: &RegionValueElements,
typeck: &mut TypeChecker<'_, 'tcx>,
value: impl TypeFoldable<'tcx>,
live_at: &IntervalSet<PointIndex>
)
fn compute_drop_data(
typeck: &mut TypeChecker<'_, 'tcx>,
dropped_ty: Ty<'tcx>
) -> DropData<'tcx>
Auto Trait Implementations
impl<'me, 'typeck, 'flow, 'tcx> !RefUnwindSafe for LivenessContext
impl<'me, 'typeck, 'flow, 'tcx> !Send for LivenessContext
impl<'me, 'typeck, 'flow, 'tcx> !Sync for LivenessContext
impl<'me, 'typeck, 'flow, 'tcx> Unpin for LivenessContext where
'flow: 'me,
'tcx: 'me,
'typeck: 'me,
impl<'me, 'typeck, 'flow, 'tcx> !UnwindSafe for LivenessContext
Blanket Implementations
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: 80 bytes