Struct rustc_borrowck::MaybeUninitializedPlaces [−][src]
pub(crate) struct MaybeUninitializedPlaces<'a, 'tcx> {
tcx: TyCtxt<'tcx>,
body: &'a Body<'tcx>,
mdpe: &'a MoveDataParamEnv<'tcx>,
mark_inactive_variants_as_uninit: bool,
}Expand description
MaybeUninitializedPlaces tracks all places that might be
uninitialized 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-uninit:
// {a, b, c, d}
let a = S; let b = S; let c; let d; // { c, d}
if pred {
drop(a); // {a, c, d}
b = S; // {a, c, d}
} else {
drop(b); // { b, c, d}
d = S; // { b, c }
} // {a, b, c, d}
c = S; // {a, b, d}
}To determine whether a place must be uninitialized at a
particular control-flow point, one can take the set-difference
between this data and the data from MaybeInitializedPlaces at the
corresponding control-flow point.
Similarly, at a given drop statement, the set-intersection
between this data and MaybeInitializedPlaces 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>mark_inactive_variants_as_uninit: boolAuto Trait Implementations
impl<'a, 'tcx> !RefUnwindSafe for MaybeUninitializedPlaces<'a, 'tcx>
impl<'a, 'tcx> !Send for MaybeUninitializedPlaces<'a, 'tcx>
impl<'a, 'tcx> !Sync for MaybeUninitializedPlaces<'a, 'tcx>
impl<'a, 'tcx> Unpin for MaybeUninitializedPlaces<'a, 'tcx> where
'tcx: 'a,
impl<'a, 'tcx> !UnwindSafe for MaybeUninitializedPlaces<'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: 32 bytes