Struct rustc_trait_selection::infer::at::At

pub struct At<'a, 'tcx> {
    pub infcx: &'a InferCtxt<'tcx>,
    pub cause: &'a ObligationCause<'tcx>,
    pub param_env: ParamEnv<'tcx>,
}

Fields

infcx: &'a InferCtxt<'tcx>

cause: &'a ObligationCause<'tcx>

param_env: ParamEnv<'tcx>

Trait Implementations

impl<'tcx> NormalizeExt<'tcx> for At<'_, 'tcx>

fn normalize<T: TypeFoldable<TyCtxt<'tcx>>>(&self, value: T) -> InferOk<'tcx, T>

Normalize a value using the AssocTypeNormalizer.

This normalization should be used when the type contains inference variables or the projection may be fallible.

fn deeply_normalize<T: TypeFoldable<TyCtxt<'tcx>>>( self, value: T, fulfill_cx: &mut dyn TraitEngine<'tcx> ) -> Result<T, Vec<FulfillmentError<'tcx>>>

Deeply normalizes value, replacing all aliases which can by normalized in the current environment. In the new solver this errors in case normalization fails or is ambiguous. This only normalizes opaque types with Reveal::All.

In the old solver this simply uses normalizes and adds the nested obligations to the fulfill_cx. This is necessary as we otherwise end up recomputing the same goals in both a temporary and the shared context which negatively impacts performance as these don’t share caching.

FIXME(-Znext-solver): This has the same behavior as traits::fully_normalize in the new solver, but because of performance reasons, we currently reuse an existing fulfillment context in the old solver. Once we also eagerly prove goals with the old solver or have removed the old solver, remove traits::fully_normalize and rename this function to At::fully_normalize.

impl<'cx, 'tcx> QueryNormalizeExt<'tcx> for At<'cx, 'tcx>

fn query_normalize<T>(self, value: T) -> Result<Normalized<'tcx, T>, NoSolution>

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

Normalize value in the context of the inference context, yielding a resulting type, or an error if value cannot be normalized. If you don’t care about regions, you should prefer normalize_erasing_regions, which is more efficient.

If the normalization succeeds and is unambiguous, returns back the normalized value along with various outlives relations (in the form of obligations that must be discharged).

N.B., this will eventually be the main means of normalizing, but for now should be used only when we actually know that normalization will succeed, since error reporting and other details are still “under development”.

This normalization should only be used when the projection does not have possible ambiguity or may not be well-formed.

After codegen, when lifetimes do not matter, it is preferable to instead use TyCtxt::normalize_erasing_regions, which wraps this procedure.

impl<'tcx> StructurallyNormalizeExt<'tcx> for At<'_, 'tcx>

fn structurally_normalize( &self, ty: Ty<'tcx>, fulfill_cx: &mut dyn TraitEngine<'tcx> ) -> Result<Ty<'tcx>, Vec<FulfillmentError<'tcx>>>

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: 24 bytes