-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Handle binder type symbols in extractor patterns #4056
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
24: Pattern Match Exhaustivity: Fun.ConstNullClass(_) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
enum Fun[-T, +U >: Null] { | ||
def f: T => U = this match { | ||
case Identity(g) => g | ||
case ConstNull => (_ => null) | ||
case ConstNullClass(y) => (_ => null) | ||
case ConstNullSimple => null | ||
} | ||
|
||
case Identity[T, U >: Null](g: T => U) extends Fun[T, U] | ||
case ConstNull | ||
case ConstNullClass(x: T) | ||
case ConstNullSimple | ||
} | ||
|
||
object Test { | ||
def main(args: Array[String]) = { | ||
val x: Null = Fun.ConstNull.f("abc") | ||
val y: Null = Fun.ConstNullClass("hello").f("abc") | ||
assert(Fun.ConstNullSimple.f == null) | ||
} | ||
|
||
import Fun._ | ||
|
||
def f[T, U >: Null](f: Fun[T, U]): T => U = f match { | ||
case Identity(g) => g | ||
case ConstNull => (_ => null) | ||
case ConstNullClass(y: Int) => (_ => null) | ||
case ConstNullSimple => null | ||
} | ||
} | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be sure: basically this throws away
_$1
and_$2
, which is fine now but might be less fine if we had type arguments for extractor patterns (which at least I'd like eventually?)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we check according to semantics, I think it's correct. I cannot come up with a counter-example. If some type cannot be checked at run-time, they get a warning instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes; since type arguments to classes/traits are erased at runtime, the only use case is for annotating what GADT inference should deduce or for binding type variables generated by GADT inference. For instance:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems the example doesn't compile at all, despite any repairing efforts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mentioned upfront the issue is with a potential future feature, so of course my example doesn't work yet: