bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

delay a bug when encountering an ambiguity in MIR typeck

Browse source
This commit is contained in:
Ali MJ Al-Nasrawy 2023-10-08 09:14:12 +00:00
parent 6d271692b0
commit 710c073acb
3 changed files with 40 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

16
compiler/rustc_trait_selection/src/traits/query/type_op/mod.rs
View file

@ -157,10 +157,18 @@ where
}
let mut region_constraints = QueryRegionConstraints::default();
let (output, error_info, mut obligations, _) =
Q::fully_perform_into(self, infcx, &mut region_constraints).map_err(|_| {
infcx.tcx.sess.delay_span_bug(span, format!("error performing {self:?}"))
})?;
let (output, error_info, mut obligations) =
Q::fully_perform_into(self, infcx, &mut region_constraints)
.map_err(|_| {
infcx.tcx.sess.delay_span_bug(span, format!("error performing {self:?}"))
})
.and_then(|(output, error_info, obligations, certainty)| match certainty {
Certainty::Proven => Ok((output, error_info, obligations)),
Certainty::Ambiguous => Err(infcx
.tcx
.sess
.delay_span_bug(span, format!("ambiguity performing {self:?}"))),
})?;
// Typically, instantiating NLL query results does not
// create obligations. However, in some cases there