-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fix #10357: Add MATCHCASEtype tag to Tasty #10362
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
Conversation
@@ -676,6 +678,7 @@ object TastyFormat { | |||
case TYPELAMBDAtype => "TYPELAMBDAtype" | |||
case LAMBDAtpt => "LAMBDAtpt" | |||
case MATCHtype => "MATCHtype" | |||
case MATCHCASEtype => "MATCHCASEtype" |
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 think TastyPrinter will need a case too.
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 don't see why?
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.
Ah maybe not, I see we don't need cases for all type nodes in the printer.
@@ -676,6 +678,7 @@ object TastyFormat { | |||
case TYPELAMBDAtype => "TYPELAMBDAtype" | |||
case LAMBDAtpt => "LAMBDAtpt" | |||
case MATCHtype => "MATCHtype" | |||
case MATCHCASEtype => "MATCHCASEtype" |
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.
Ah maybe not, I see we don't need cases for all type nodes in the printer.
The failure in |
Thanks @romanowski, looks like |
@smarter I wonder if we should not include a path or any other way to quickly detect which |
We thus avoid references to a "magic" scala.internal.MatchCase class.
59453c3
to
90cdf18
Compare
We thus avoid references to a "magic" scala.internal.MatchCase class.