Module infer_ctxt 

Re-exports

use core::fmt; 🔒

use std::hash::Hash; 🔒

use std::hash::Hash; 🔒

use std::hash::Hasher; 🔒

use std::range::RangeInclusive; 🔒

use derive_where::derive_where; 🔒

use rustc_macros::Decodable_NoContext; 🔒

use rustc_macros::Encodable_NoContext; 🔒

use rustc_macros::StableHash_NoContext; 🔒

use crate::data_structures::DelayedMap; 🔒

use crate::relate::RelateResult; 🔒

use crate::relate::combine::PredicateEmittingRelation; 🔒

use crate::solve::TyOrConstInferVar; 🔒

use crate::solve::VisibleForLeakCheck; 🔒

use crate as ty; 🔒

use crate::CallerBoundsIterator; 🔒

use crate::Const; 🔒

use crate::Interner; 🔒

use crate::PredicateProxy; 🔒

use crate::Region; 🔒

use crate::TyVid; 🔒

use crate::TypeFoldable; 🔒

use crate::TypeFolder; 🔒

use crate::TypeSuperFoldable; 🔒

use crate::TypeVisitableExt; 🔒

use crate::inherent::*; 🔒

Modules

private 🔒

Structs

DeepVariableResolver 🔒

MayBeErased

TypingModeEqWrapper

We want to highly discourage using equality checks on typing modes. Instead you should match, exhaustively, so when we ever modify the enum we get a compile error. Only use TypingModeEqWrapper when you really really really have to. Prefer unwrapping TypingModeEqWrapper in apis that should return a TypingMode whenever possible, and if you ever get an TypingModeEqWrapper, prefer unwrapping it and matching on it exhaustively.

Enums

CantBeErased

TypingMode

The current typing mode of an inference context. We unfortunately have some slightly different typing rules depending on the current context. See the doc comment for each variant for how and why they are used.

Traits

InferCtxtLike

InferCtxtLike is one of the two traits abstracting over the InferCtxt, which had to be split due to coherence reasons:

TypingModeErasedStatus

Functions

may_use_unstable_feature