-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[spec] remove implementation details from enum spec #18579
Conversation
bishabosha
commented
Sep 21, 2023
•
edited
Loading
edited
- remove details that force all explicit extends clauses to have unique anonymous classes. Perhaps we can find a way in the future to desugar explicit extends clauses to the same implementation class
- also cleanup definitions of rules
```scala | ||
case ´C_1´; ...; case ´C_n´ | ||
``` | ||
Any modifiers or annotations on the original case extend to all expanded cases. | ||
This result is then further rewritten by either (3 or 4). | ||
<p>This result is then further rewritten by either (3 or 4).</p> |
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.
Does that actually render in a meaningful way?
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 thought it looks nicer with the clean break, there's no way to do that in pure markdown without breaking the numbered list
@sjrd addressed the comments, we should probably review individual definition words, such as "enum class" and "unparameterized" later, as these seem to cause confusion unless you pay attention to every detail |