fix: normalize projection after discarding free BoundVar
s in RPIT
#13750
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 #13307
When we lower the return type of a function, it may contain free
BoundVar
s inOpaqueType
's substitution, which would cause panic during canonicalization as part of projection normalization. ThoseBoundVar
s are irrelevant in this context and will be discarded, and we should defer projection normalization until then.