Do not eagerly fold consts in normalize_param_env_or_error
if new solver
#141332
+11
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes rust-lang/trait-system-refactor-initiative#213
Given:
when elaborating param env for
Trait
, we haveSelf: Trait
,Self: Deref<Target = [u8; {anon const}]>
.Before this PR, we would fold the anon consts away before elaborating. However, we end up getting another un-folded copy of the anon const from elaborating
Self: Trait
. This leads to normalization ambiguity.r? lcnr