Struct DefinitelyInitializedPlaces

pub struct DefinitelyInitializedPlaces<'a, 'tcx> {
    body: &'a Body<'tcx>,
    move_data: &'a MoveData<'tcx>,
}

DefinitelyInitializedPlaces tracks all places that are definitely 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) {                        // definite-init:
                                            // {          }
    let a = S; let mut b = S; let c; let d; // {a, b      }

    if pred {
        drop(a);                            // {   b,     }
        b = S;                              // {   b,     }

    } else {
        drop(b);                            // {a,        }
        d = S;                              // {a,       d}

    }                                       // {          }

    c = S;                                  // {       c  }
}

To determine whether a place may be uninitialized at a particular control-flow point, one can take the set-complement of this data.

Similarly, at a given drop statement, the set-difference between this data and MaybeInitializedPlaces yields the set of places that would require a dynamic drop-flag at that statement.

Fields

body: &'a Body<'tcx>

move_data: &'a MoveData<'tcx>

Implementations

impl<'a, 'tcx> DefinitelyInitializedPlaces<'a, 'tcx>

pub fn new(body: &'a Body<'tcx>, move_data: &'a MoveData<'tcx>) -> Self

impl<'a, 'tcx> DefinitelyInitializedPlaces<'a, 'tcx>

fn update_bits( trans: &mut Dual<BitSet<MovePathIndex>>, path: MovePathIndex, state: DropFlagState, )

Trait Implementations

impl<'a, 'tcx> Analysis<'tcx> for DefinitelyInitializedPlaces<'a, 'tcx>

type Domain = Dual<BitSet<MovePathIndex>>

Use set intersection as the join operator.

const NAME: &'static str = "definite_init"

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

fn bottom_value(&self, _: &Body<'tcx>) -> Self::Domain

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

fn initialize_start_block(&self, _: &Body<'tcx>, state: &mut Self::Domain)

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

fn apply_statement_effect( &mut self, trans: &mut Self::Domain, _statement: &Statement<'tcx>, location: Location, )

Updates the current dataflow state with the effect of evaluating a statement.

fn apply_terminator_effect<'mir>( &mut self, trans: &mut Self::Domain, terminator: &'mir Terminator<'tcx>, location: Location, ) -> TerminatorEdges<'mir, 'tcx>

Updates the current dataflow state with the effect of evaluating a terminator.

fn apply_call_return_effect( &mut self, trans: &mut Self::Domain, _block: BasicBlock, return_places: CallReturnPlaces<'_, 'tcx>, )

Updates the current dataflow state with the effect of a successful return from a Call terminator.

type Direction = Forward

The direction of this analysis. Either Forward or Backward.

fn apply_before_statement_effect( &mut self, _state: &mut Self::Domain, _statement: &Statement<'tcx>, _location: Location, )

Updates the current dataflow state with an effect that occurs immediately before the given statement.

fn apply_before_terminator_effect( &mut self, _state: &mut Self::Domain, _terminator: &Terminator<'tcx>, _location: Location, )

Updates the current dataflow state with an effect that occurs immediately before the given terminator.

fn apply_switch_int_edge_effects( &mut self, _block: BasicBlock, _discr: &Operand<'tcx>, _apply_edge_effects: &mut impl SwitchIntEdgeEffects<Self::Domain>, )

Updates the current dataflow state with the effect of taking a particular branch in a SwitchInt terminator.

fn into_engine<'mir>( self, tcx: TyCtxt<'tcx>, body: &'mir Body<'tcx>, ) -> Engine<'mir, 'tcx, Self>

where Self: Sized,

Creates an Engine to find the fixpoint for this dataflow problem.

impl<'a, 'tcx> HasMoveData<'tcx> for DefinitelyInitializedPlaces<'a, 'tcx>

fn move_data(&self) -> &MoveData<'tcx>

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