-
Notifications
You must be signed in to change notification settings - Fork 13.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
syntax: use MetaPath (a simpler version of Path) for Attribute and MetaItem. #56492
Conversation
a3f5490
to
778e1b6
Compare
778e1b6
to
3b5f818
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Didn't have a chance to look at this in detail today, but I'm pretty skeptical about the idea in general. With two kinds of paths there's now a chance to visit/fold all paths, but forget attribute paths accidentally. |
The description for #56480 covers that a bit. The problem is we have
This is already an issue, e.g. |
r=me for the first two commits, see #56480 regarding the third one. |
☔ The latest upstream changes (presumably #54517) made this pull request unmergeable. Please resolve the merge conflicts. |
@petrochenkov What do you think of the newtype of |
Seems ok. |
@petrochenkov Just customize |
Triage; @eddyb Hello, have you been able to get back to this PR? |
Ping from triage @eddyb: What is the status of this PR? |
ping from triage @eddyb Unfortunately we haven't heard from you on this in a while, so I'm closing the PR to keep things tidy. Don't worry though, if you'll have time again in the future please reopen this PR, we'll be happy to review it again! |
This is the simpler alternative to #56480, and has two advantages:
{ast,hir}::PathSegment
in attribute pathsuse
and attributesr? @petrochenkov cc @nikomatsakis