Fix name resolution in typealias
with constraint
#144
Merged
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.
The body of a
typealias
gets inlined into wherever thetypealias
is used. This fixes a bug where the name resolution would resolve an additional type constraint on the next scope ofthis
.Lack of a frame scope
typealias
doesn't currently have a frame scope, which is why we have to assign theowner
and thereceiver
here. If it did, we could read both of these at the point where we're trying to resolve thetypealias
in question.