Module regions 

Re-exports

use rustc_data_structures::fx::FxIndexSet; 🔒

use rustc_hir::def_id::LocalDefId; 🔒

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

use rustc_infer::infer::InferCtxt; 🔒

use rustc_infer::infer::RegionResolutionError; 🔒

use rustc_infer::infer::SubregionOrigin; 🔒

use rustc_infer::infer::TyCtxtInferExt; 🔒

use rustc_infer::infer::TypeOutlivesConstraint; 🔒

use rustc_macros::extension; 🔒

use rustc_middle::traits::ObligationCause; 🔒

use rustc_middle::ty; 🔒

use rustc_middle::ty::CallerBoundsIterator; 🔒

use rustc_middle::ty::Ty; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_middle::ty::TypeVisitableExt; 🔒

use rustc_middle::ty::TypingMode; 🔒

use rustc_middle::ty::Unnormalized; 🔒

use rustc_middle::ty::elaborate; 🔒

use rustc_span::DUMMY_SP; 🔒

use crate::traits::ScrubbedTraitError; 🔒

use crate::traits::outlives_bounds::InferCtxtExt; 🔒

Traits

InferCtxtRegionExt

OutlivesEnvironmentBuildExt

Functions

region_known_to_outlive

Given a known param_env and a set of well formed types, can we prove that region_a outlives region_b

test_region_obligations

Given a known param_env and a set of well formed types, set up an InferCtxt, call the passed function (to e.g. set up region constraints to be tested), then resolve region and return errors

ty_known_to_outlive

Given a known param_env and a set of well formed types, can we prove that ty outlives region.