Normalize before computing ConstArgHasType goal in new solver #142806
+18
−6
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.
This is a fix for #139905. See the description I left in the test.
I chose to fix this by normalizing the type before matching on its
.kind()
incompute_const_arg_has_type_goal
(since it feels somewhat consistent with how we normalize types before assembling their candidates, for example); however, there are several other solutions that come to mind for fixing this ICE:ConstKind::Error
a proper type, likeConstKind::Value
, so that consts don't go from failing to passingConstArgHasType
goals after normalization (i.e.UNEVALUATED
would normalize into aConstKind::Error(_, bool)
type rather than losing its type altogether).Thoughts? Happy to discuss this fix further.
r? @BoxyUwU