Module select 

Re-exports

use std::ops::ControlFlow; 🔒

use rustc_infer::infer::InferCtxt; 🔒

use rustc_infer::traits::solve::inspect::ProbeKind; 🔒

use rustc_infer::traits::solve::CandidateSource; 🔒

use rustc_infer::traits::solve::Certainty; 🔒

use rustc_infer::traits::solve::Goal; 🔒

use rustc_infer::traits::solve::ParamEnvSource; 🔒

use rustc_infer::traits::BuiltinImplSource; 🔒

use rustc_infer::traits::ImplSource; 🔒

use rustc_infer::traits::ImplSourceUserDefinedData; 🔒

use rustc_infer::traits::Obligation; 🔒

use rustc_infer::traits::ObligationCause; 🔒

use rustc_infer::traits::PolyTraitObligation; 🔒

use rustc_infer::traits::Selection; 🔒

use rustc_infer::traits::SelectionError; 🔒

use rustc_infer::traits::SelectionResult; 🔒

use rustc_macros::extension; 🔒

use rustc_span::Span; 🔒

use rustc_span::bug; 🔒

use rustc_span::span_bug; 🔒

use thin_vec::thin_vec; 🔒

use crate::solve::inspect; 🔒

use crate::solve::inspect::InferCtxtProofTreeExt; 🔒

Structs

Select 🔒

Traits

InferCtxtSelectExt

Functions

candidate_should_be_dropped_in_favor_of 🔒

This is a lot more limited than the old solver’s equivalent method. This may lead to more Ok(None) results when selecting traits in polymorphic contexts, but we should never rely on the lack of ambiguity, and should always just gracefully fail here. We shouldn’t rely on this incompleteness.

to_selection 🔒