-
-
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
fix #34080, regression in printing qualified macro calls #34081
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.
Looks great to me.
print(io, arg1.args[1]) | ||
print(io, ").") | ||
m = arg1.args[1] | ||
if m isa Symbol || m isa GlobalRef || is_expr(m, :(.), 2) |
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.
Very minor: should we also allow m isa Module
here in case people interpolate a module into the AST?
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.
The previous version of the code parenthesized Modules, but I'm not sure why. I guess we'd need $
to be super accurate about it.
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.
Good point, it would be nice to generally show the difference between purely symbolic ASTs vs ASTs which have "unusual" objects interpolated into them. Especially for things like modules which show
the same way as symbols.
Doesn't backport cleanly. |
@KristofferC what's the procedure to do a complex backport? PR against the backports branch? |
Yes, a PR against the backports branch should be fine. Thanks for handling this!! ❤️ |
Can also just push directly to the backports branch. |
fix #34080