not knowing about opaque types is worse than not knowing about regions, make sure we don't accidentally mark something as ok-modulo-regions if there are opaque types involved
This commit is contained in:
@@ -174,12 +174,12 @@ pub enum SelectionCandidate<'tcx> {
|
|||||||
pub enum EvaluationResult {
|
pub enum EvaluationResult {
|
||||||
/// Evaluation successful.
|
/// Evaluation successful.
|
||||||
EvaluatedToOk,
|
EvaluatedToOk,
|
||||||
|
/// Evaluation successful, but there were unevaluated region obligations.
|
||||||
|
EvaluatedToOkModuloRegions,
|
||||||
/// Evaluation successful, but need to rerun because opaque types got
|
/// Evaluation successful, but need to rerun because opaque types got
|
||||||
/// hidden types assigned without it being known whether the opaque types
|
/// hidden types assigned without it being known whether the opaque types
|
||||||
/// are within their defining scope
|
/// are within their defining scope
|
||||||
EvaluatedToOkModuloOpaqueTypes,
|
EvaluatedToOkModuloOpaqueTypes,
|
||||||
/// Evaluation successful, but there were unevaluated region obligations.
|
|
||||||
EvaluatedToOkModuloRegions,
|
|
||||||
/// Evaluation is known to be ambiguous -- it *might* hold for some
|
/// Evaluation is known to be ambiguous -- it *might* hold for some
|
||||||
/// assignment of inference variables, but it might not.
|
/// assignment of inference variables, but it might not.
|
||||||
///
|
///
|
||||||
|
|||||||
Reference in New Issue
Block a user