Struct rustc_typeck::traits::FulfillmentContext [−][src]
pub struct FulfillmentContext<'tcx> {
predicates: ObligationForest<PendingPredicateObligation<'tcx>>,
relationships: HashMap<TyVid, FoundRelationships, BuildHasherDefault<FxHasher>>,
register_region_obligations: bool,
usable_in_snapshot: bool,
}Expand description
The fulfillment context is used to drive trait resolution. It
consists of a list of obligations that must be (eventually)
satisfied. The job is to track which are satisfied, which yielded
errors, and which are still pending. At any point, users can call
select_where_possible, and the fulfillment context will try to do
selection, retaining only those obligations that remain
ambiguous. This may be helpful in pushing type inference
along. Once all type inference constraints have been generated, the
method select_all_or_error can be used to report any remaining
ambiguous cases as errors.
Fields
predicates: ObligationForest<PendingPredicateObligation<'tcx>>relationships: HashMap<TyVid, FoundRelationships, BuildHasherDefault<FxHasher>>register_region_obligations: boolusable_in_snapshot: boolAuto Trait Implementations
impl<'tcx> !RefUnwindSafe for FulfillmentContext<'tcx>
impl<'tcx> !Send for FulfillmentContext<'tcx>
impl<'tcx> !Sync for FulfillmentContext<'tcx>
impl<'tcx> Unpin for FulfillmentContext<'tcx>
impl<'tcx> !UnwindSafe for FulfillmentContext<'tcx>
Blanket Implementations
Mutably borrows from an owned value. Read more
pub fn register_predicate_obligations(
&mut self,
infcx: &InferCtxt<'_, 'tcx>,
obligations: impl IntoIterator<Item = Obligation<'tcx, Predicate<'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: 200 bytes