Projection types in user annotations may contain inference variables. This makes the normalization depend on the unification with the actual type and thus requires a separate TypeOp to track the obligations. Otherwise simply calling `TypeChecker::normalize` would ICE with "unexpected ambiguity" |
||
|---|---|---|
| .. | ||
| chalk | ||
| codegen.rs | ||
| dropck_outlives.rs | ||
| evaluate_obligation.rs | ||
| implied_outlives_bounds.rs | ||
| lib.rs | ||
| normalize_erasing_regions.rs | ||
| normalize_projection_ty.rs | ||
| type_op.rs | ||