Module opaque_types 

Re-exports

use rustc_data_structures::fx::FxIndexMap; 🔒

use rustc_hir::OpaqueTyOrigin; 🔒

use rustc_hir::def_id::LocalDefId; 🔒

use rustc_infer::infer::outlives::env::OutlivesEnvironment; 🔒

use rustc_infer::infer::InferCtxt; 🔒

use rustc_infer::infer::TyCtxtInferExt; 🔒

use rustc_middle::ty; 🔒

use rustc_middle::ty::DefiningScopeKind; 🔒

use rustc_middle::ty::GenericArgKind; 🔒

use rustc_middle::ty::GenericArgs; 🔒

use rustc_middle::ty::OpaqueTypeKey; 🔒

use rustc_middle::ty::Ty; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_middle::ty::TypeVisitableExt; 🔒

use rustc_middle::ty::TypingMode; 🔒

use rustc_middle::ty::fold_regions; 🔒

use rustc_span::ErrorGuaranteed; 🔒

use rustc_span::Span; 🔒

use crate::diagnostics::NonGenericOpaqueTypeParam; 🔒

use crate::regions::OutlivesEnvironmentBuildExt; 🔒

use crate::traits::ObligationCtxt; 🔒

Structs

LazyOpaqueTyEnv 🔒

Computes if an opaque type requires a lifetime parameter to be equal to another one or to the 'static lifetime. These requirements are derived from the explicit and implied bounds.

Enums

NonDefiningUseReason

Functions

opaque_type_has_defining_use_args

Opaque type parameter validity check as documented in the rustc-dev-guide chapter. With the new solver, uses which fail this check are simply treated as non-defining and we only emit an error if no defining use exists.

report_item_does_not_constrain_error