Expand description
VM rules for pointer-preserving calls and owner lifetimes.
Re-exportsยง
use std::collections::HashMap;๐use rustc_hir::def_id::DefId;๐use rustc_middle::mir::Body;๐use rustc_middle::mir::Operand;๐use rustc_middle::mir::ProjectionElem;๐use rustc_middle::mir::StatementKind;๐use rustc_middle::mir::TerminatorKind;๐use rustc_middle::ty::Ty;๐use rustc_middle::ty::TyCtxt;๐use rustc_middle::ty::TyKind;๐use crate::analysis::dataflow::pointer_flow::is_nonnull_view;๐use crate::analysis::dataflow::pointer_flow::return_source_arg;๐use crate::util::mir_utils;๐
Functionsยง
- callsite_
replaces_ ๐pointer_ field - Whether a callee can replace a pointer stored in one of its objects. This follows MIR calls rather than identifying container methods by name.
- is_
benign_ ๐origin_ use - Whether MIR shows a read-only pointer view of the first argument.
- is_
pointer_ ๐storage_ ty - is_
read_ ๐only_ nonnull_ view - A
NonNullview that leaves its input allocation unchanged. - is_
read_ ๐only_ return - A pointer result from a single, side-effect-free MIR block is safe to use while tracking an existing pointer origin.
- replaces_
pointer_ ๐field_ rec - returns_
undropped_ ๐arg - A consumed owner remains allocated when a side-effect-free MIR body returns its pointer without running a destructor.
- single_
block_ ๐without_ effects - A single return block with no writes through a dereferenced place.