Module needs_drop 

Check whether a type has (potentially) non-trivial drop glue.

Re-exports

use rustc_attr_ir::find_attr; 🔒

use rustc_data_structures::fx::FxHashSet; 🔒

use rustc_hir::def_id::DefId; 🔒

use rustc_middle::query::Providers; 🔒

use rustc_middle::ty::util::AlwaysRequiresDrop; 🔒

use rustc_middle::ty::util::needs_drop_components; 🔒

use rustc_middle::ty; 🔒

use rustc_middle::ty::EarlyBinder; 🔒

use rustc_middle::ty::GenericArgs; 🔒

use rustc_middle::ty::Ty; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_middle::ty::Unnormalized; 🔒

use rustc_span::bug; 🔒

use rustc_structures::Limit; 🔒

use tracing::debug; 🔒

use tracing::instrument; 🔒

use tracing::instrument; 🔒

use crate::diagnostics::NeedsDropOverflow; 🔒

Structs

DropTysOptions 🔒

NeedsDropTypes 🔒

Enums

DtorType 🔒

Functions

adt_async_drop_tys 🔒

adt_consider_insignificant_dtor 🔒

adt_drop_tys 🔒

adt_significant_drop_tys 🔒

drop_tys_helper 🔒

filter_array_elements 🔒

HACK: in order to not mistakenly assume that [PhantomData<T>; N] requires drop glue we check the element type for drop glue. The correct fix would be looking at the entirety of the code around needs_drop_components and this file and come up with logic that is easier to follow while not repeating any checks that may thus diverge.

filter_array_elements_async 🔒

has_significant_drop_raw 🔒

list_significant_drop_tys 🔒

needs_async_drop_raw 🔒

needs_drop_raw 🔒

provide 🔒

Type Aliases

NeedsDropResult 🔒