if we have an ocx, use it

This commit is contained in:
lcnr 2024-08-14 09:36:53 +02:00
parent 9859bf27fd
commit 3a02047d52

View file

@ -170,44 +170,12 @@ where
// collecting region constraints via `region_constraints`. // collecting region constraints via `region_constraints`.
let (mut output, _) = scrape_region_constraints( let (mut output, _) = scrape_region_constraints(
infcx, infcx,
|_ocx| { |ocx| {
let (output, ei, mut obligations, _) = let (output, ei, obligations, _) =
Q::fully_perform_into(self, infcx, &mut region_constraints, span)?; Q::fully_perform_into(self, infcx, &mut region_constraints, span)?;
error_info = ei; error_info = ei;
// Typically, instantiating NLL query results does not ocx.register_obligations(obligations);
// create obligations. However, in some cases there
// are unresolved type variables, and unify them *can*
// create obligations. In that case, we have to go
// fulfill them. We do this via a (recursive) query.
while !obligations.is_empty() {
trace!("{:#?}", obligations);
let mut progress = false;
for obligation in std::mem::take(&mut obligations) {
let obligation = infcx.resolve_vars_if_possible(obligation);
match ProvePredicate::fully_perform_into(
obligation.param_env.and(ProvePredicate::new(obligation.predicate)),
infcx,
&mut region_constraints,
span,
) {
Ok(((), _, new, certainty)) => {
obligations.extend(new);
progress = true;
if let Certainty::Ambiguous = certainty {
obligations.push(obligation);
}
}
Err(_) => obligations.push(obligation),
}
}
if !progress {
infcx.dcx().span_bug(
span,
format!("ambiguity processing {obligations:?} from {self:?}"),
);
}
}
Ok(output) Ok(output)
}, },
"fully_perform", "fully_perform",