[Draft] A more dependent pattern matching prototype #21828
Draft
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.
Sometime, it is useful to track the dependency between the selector and the pattern-bind variable.
Given the example, in the body of the case, we should be able to tell:
a
andb
are the same reference;a.x
,b.x
andy
are same as well.This PR made following modifications:
i
th parameterx: T
, ifx
is not avar
, generatedef _i: this.x = this.x
, instead ofdef _i: T = this.x
.unapply
for a case classA
becomesdef unapply(a: A): a.type = a
.TermRef
s when typing patterns. Ifpt
is a singleton type, we use intersection to addpt
to the new pattern-bind variable.With this PR, the following code can be type checked: