-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
expand: Stop normalizing NtIdent
s before passing them to built-in macros
#77275
Conversation
r? @varkor (rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ rollup |
📌 Commit 3b27799 has been approved by |
expand: Stop normalizing `NtIdent`s before passing them to built-in macros Built-in macros should be able to deal with `NtIdents` in the input by themselves like any other parser code. You can't imagine how bad mutable AST visitors are, *especially* if they are modifying tokens. This is one step towards removing token visiting from the visitor infrastructure (rust-lang#77271 also works in this direction.)
I think this broke the @bors r- rollup=iffy |
Yep, this PR is to blame. |
…-in macros This was a big hack, and built-in macros should be able to deal with `NtIdents` in the input by themselves like any other parser code.
3b27799
to
4a4a7f8
Compare
@bors r=varkor |
📌 Commit 4a4a7f8 has been approved by |
⌛ Testing commit 4a4a7f8 with merge a0aa59c155b4edde00742e095cdfb552cdf200f9... |
💥 Test timed out |
@bors retry |
☀️ Test successful - checks-actions, checks-azure |
Built-in macros should be able to deal with
NtIdents
in the input by themselves like any other parser code.You can't imagine how bad mutable AST visitors are, especially if they are modifying tokens.
This is one step towards removing token visiting from the visitor infrastructure (#77271 also works in this direction.)