Module elaborate_drops 

Re-exports

use std::fmt; 🔒

use rustc_abi::FieldIdx; 🔒

use rustc_abi::VariantIdx; 🔒

use rustc_index::IndexVec; 🔒

use rustc_index::bit_set::DenseBitSet; 🔒

use rustc_middle::ty; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_mir_dataflow::impls::MaybeInitializedPlaces; 🔒

use rustc_mir_dataflow::impls::MaybeUninitializedPlaces; 🔒

use rustc_mir_dataflow::move_paths::LookupResult; 🔒

use rustc_mir_dataflow::move_paths::MoveData; 🔒

use rustc_mir_dataflow::move_paths::MovePathIndex; 🔒

use rustc_mir_dataflow::Analysis; 🔒

use rustc_mir_dataflow::DropFlagState; 🔒

use rustc_mir_dataflow::MoveDataTypingEnv; 🔒

use rustc_mir_dataflow::ResultsCursor; 🔒

use rustc_mir_dataflow::on_all_children_bits; 🔒

use rustc_mir_dataflow::on_lookup_result_bits; 🔒

use rustc_span::Span; 🔒

use tracing::debug; 🔒

use tracing::instrument; 🔒

use tracing::instrument; 🔒

use crate::PassPolicy; 🔒

use crate::elaborate_drop::DropElaborator; 🔒

use crate::elaborate_drop::DropFlagMode; 🔒

use crate::elaborate_drop::DropStyle; 🔒

use crate::elaborate_drop::Unwind; 🔒

use crate::elaborate_drop::elaborate_drop; 🔒

use crate::patch::MirPatch; 🔒

use rustc_middle::mir::*; 🔒

Structs

ElaborateDrops 🔒

During MIR building, Drop terminators are inserted in every place where a drop may occur. However, in this phase, the presence of these terminators does not guarantee that a destructor will run, as the target of the drop may be uninitialized. In general, the compiler cannot determine at compile time whether a destructor will run or not.

ElaborateDropsCtxt 🔒

InitializationData 🔒

Functions

compute_dead_unwinds 🔒

Records unwind edges which are known to be unreachable, because they are in drop terminators that can’t drop anything.