-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
rename expression heads for type definitions to match keywords #23157
Conversation
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.
superficially lgtm! :)
I don't suppose there's any way to deprecate the old expression heads? I know a couple packages are using |
Yes, I can deprecate that particular use pattern. |
5b56e13
to
acadf3a
Compare
Done. While I'm at it, I also changed the parsed representation to match the order that the subexpressions appear in the source. |
NEWS.md
Outdated
@@ -35,6 +35,13 @@ Language changes | |||
* Nested `if` expressions that arise from the keyword `elseif` now use `elseif` | |||
as their expression head instead of `if` ([#21774]). | |||
|
|||
* Parsed and lowered forms of type definitions have been synchronized with their | |||
new keywords ([#23157]). Expression heads are renamed as follows: | |||
`type` => `struct` |
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.
Perhaps add *
s on this list with 4 space indent to render it as a bullet list? Current rendering looks a bit funny https://github.com/JuliaLang/julia/blob/acadf3acb6054adb657d6a9390616f2c1e792546/NEWS.md#language-changes
acadf3a
to
6452535
Compare
...that automatically use the correct expression head to deal with JuliaLang/julia#23157.
No description provided.