Struct rustc_borrowck::MaybeInitializedPlaces [−][src]
pub(crate) struct MaybeInitializedPlaces<'a, 'tcx> {
tcx: TyCtxt<'tcx>,
body: &'a Body<'tcx>,
mdpe: &'a MoveDataParamEnv<'tcx>,
}Expand description
MaybeInitializedPlaces tracks all places that might be
initialized upon reaching a particular point in the control flow
for a function.
For example, in code like the following, we have corresponding dataflow information shown in the right-hand comments.
struct S;
fn foo(pred: bool) { // maybe-init:
// {}
let a = S; let b = S; let c; let d; // {a, b}
if pred {
drop(a); // { b}
b = S; // { b}
} else {
drop(b); // {a}
d = S; // {a, d}
} // {a, b, d}
c = S; // {a, b, c, d}
}To determine whether a place must be initialized at a
particular control-flow point, one can take the set-difference
between this data and the data from MaybeUninitializedPlaces at the
corresponding control-flow point.
Similarly, at a given drop statement, the set-intersection
between this data and MaybeUninitializedPlaces yields the set of
places that would require a dynamic drop-flag at that statement.
Fields
tcx: TyCtxt<'tcx>body: &'a Body<'tcx>mdpe: &'a MoveDataParamEnv<'tcx>Auto Trait Implementations
impl<'a, 'tcx> !RefUnwindSafe for MaybeInitializedPlaces<'a, 'tcx>
impl<'a, 'tcx> !Send for MaybeInitializedPlaces<'a, 'tcx>
impl<'a, 'tcx> !Sync for MaybeInitializedPlaces<'a, 'tcx>
impl<'a, 'tcx> Unpin for MaybeInitializedPlaces<'a, 'tcx> where
'tcx: 'a,
impl<'a, 'tcx> !UnwindSafe for MaybeInitializedPlaces<'a, 'tcx>
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: 24 bytes