-
Notifications
You must be signed in to change notification settings - Fork 13.4k
syntax: Remove Nt(Impl,Trait,Foreign)Item
#69423
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
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.
Thanks. I wonder whether we have a test for trait items specifically that exercises the interaction with NtTraitItem
and parameter names on Rust 2015. It doesn't seem like this would cause any problems re. that as Annotatable::TraitItem
s would still cause us to parse using parse_trait_item
. But could you double check? r=me with that and these comments considered.
These nonterminals shouldn't be observable during parsing, they are an implementation details of, well, not even expansion, but pretty-printing. After #62667 tokens streams themselves are printed pretty nicely, so I want to try removing this piece of code in |
Updated. |
@bors r=Centril |
📌 Commit d134385 has been approved by |
syntax: Remove `Nt(Impl,Trait,Foreign)Item` Follow-up to rust-lang#69366. r? @Centril
Rollup of 7 pull requests Successful merges: - #67637 (Add primitive module to libcore) - #69387 (Deduplicate identifier printing a bit) - #69412 (Mark attributes consumed by `check_mod_attrs` as normal) - #69423 (syntax: Remove `Nt(Impl,Trait,Foreign)Item`) - #69429 (remove redundant clones and import) - #69457 (Clean up e0370 e0371) - #69468 ([master] Backport release notes of 1.41.1) Failed merges: r? @ghost
[experiment] expand: Stop using nonterminals when passing items to proc macro attributes Implement the suggestion from #69423 (comment). r? @ghost
Follow-up to #69366.
r? @Centril