Struct NllTypeRelating 

struct NllTypeRelating<'a, 'b, 'tcx> {
    type_checker: &'a mut TypeChecker<'b, 'tcx>,
    locations: Locations,
    category: ConstraintCategory<'tcx>,
    universe_info: UniverseInfo<'tcx>,
    ambient_variance: Variance,
    ambient_variance_info: VarianceDiagInfo<TyCtxt<'tcx>>,
}

Fields

type_checker: &'a mut TypeChecker<'b, 'tcx>

locations: Locations

Where (and why) is this relation taking place?

category: ConstraintCategory<'tcx>

What category do we assign the resulting 'a: 'b relationships?

universe_info: UniverseInfo<'tcx>

Information so that error reporting knows what types we are relating when reporting a bound region error.

ambient_variance: Variance

How are we relating a and b?

• Covariant means a <: b.
• Contravariant means b <: a.
• Invariant means a == b.
• Bivariant means that it doesn’t matter.

ambient_variance_info: VarianceDiagInfo<TyCtxt<'tcx>>

Implementations

impl<'a, 'b, 'tcx> NllTypeRelating<'a, 'b, 'tcx>

fn new( type_checker: &'a mut TypeChecker<'b, 'tcx>, locations: Locations, category: ConstraintCategory<'tcx>, universe_info: UniverseInfo<'tcx>, ambient_variance: Variance, ) -> Self

fn ambient_covariance(&self) -> bool

fn ambient_contravariance(&self) -> bool

fn relate_opaques(&mut self, a: Ty<'tcx>, b: Ty<'tcx>) -> RelateResult<'tcx, ()>

fn enter_forall<T, U>( &mut self, binder: Binder<'tcx, T>, f: impl FnOnce(&mut Self, T) -> U, ) -> U

where T: TypeFoldable<TyCtxt<'tcx>> + Copy,

fn instantiate_binder_with_existentials<T>( &mut self, binder: Binder<'tcx, T>, ) -> T

where T: TypeFoldable<TyCtxt<'tcx>> + Copy,

fn create_next_universe(&mut self) -> UniverseIndex

fn next_existential_region_var(&mut self, name: Option<Symbol>) -> Region<'tcx>

fn next_placeholder_region( &mut self, placeholder: PlaceholderRegion<'tcx>, ) -> Region<'tcx>

fn push_outlives( &mut self, sup: Region<'tcx>, sub: Region<'tcx>, info: VarianceDiagInfo<TyCtxt<'tcx>>, )

Trait Implementations

impl<'b, 'tcx> PredicateEmittingRelation<InferCtxt<'tcx>> for NllTypeRelating<'_, 'b, 'tcx>

fn span(&self) -> Span

fn structurally_relate_aliases(&self) -> StructurallyRelateAliases

Whether aliases should be related structurally. This is pretty much always No unless you’re equating in some specific locations of the new solver. See the comments in these use-cases for more details.

fn param_env(&self) -> ParamEnv<'tcx>

fn register_predicates( &mut self, obligations: impl IntoIterator<Item: Upcast<TyCtxt<'tcx>, Predicate<'tcx>>>, )

Register predicates that must hold in order for this relation to hold. This uses the default param_env of the obligation.

fn register_goals( &mut self, obligations: impl IntoIterator<Item = Goal<'tcx, Predicate<'tcx>>>, )

Register obligations that must hold in order for this relation to hold

fn register_alias_relate_predicate(&mut self, a: Ty<'tcx>, b: Ty<'tcx>)

Register AliasRelate obligation(s) that both types must be related to each other.

impl<'b, 'tcx> TypeRelation<TyCtxt<'tcx>> for NllTypeRelating<'_, 'b, 'tcx>

fn cx(&self) -> TyCtxt<'tcx>

fn relate_ty_args( &mut self, a_ty: Ty<'tcx>, b_ty: Ty<'tcx>, def_id: DefId, a_args: GenericArgsRef<'tcx>, b_args: GenericArgsRef<'tcx>, _: impl FnOnce(GenericArgsRef<'tcx>) -> Ty<'tcx>, ) -> RelateResult<'tcx, Ty<'tcx>>

fn relate_with_variance<T: Relate<TyCtxt<'tcx>>>( &mut self, variance: Variance, info: VarianceDiagInfo<TyCtxt<'tcx>>, a: T, b: T, ) -> RelateResult<'tcx, T>

Switch variance for the purpose of relating a and b.

fn tys(&mut self, a: Ty<'tcx>, b: Ty<'tcx>) -> RelateResult<'tcx, Ty<'tcx>>

fn regions( &mut self, a: Region<'tcx>, b: Region<'tcx>, ) -> RelateResult<'tcx, Region<'tcx>>

fn consts( &mut self, a: Const<'tcx>, b: Const<'tcx>, ) -> RelateResult<'tcx, Const<'tcx>>

fn binders<T>( &mut self, a: Binder<'tcx, T>, b: Binder<'tcx, T>, ) -> RelateResult<'tcx, Binder<'tcx, T>>

where T: Relate<TyCtxt<'tcx>>,

fn relate<T>(&mut self, a: T, b: T) -> Result<T, TypeError<I>>

where T: Relate<I>,

Generic relation routine suitable for most anything.

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 88 bytes