Skip to content

Issues: rust-lang/rust

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
5 Open 1 Closed
5 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Should tokens passed through macro_rules be able to join? A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-proc-macro-back-compat Area: Backwards compatibility hacks for proc macros C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue. WG-macros Working group: Macros
#127123 opened Jun 29, 2024 by petrochenkov
2
Tracking issue for future-incompatibility lint proc_macro_derive_resolution_fallback A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. A-proc-macro-back-compat Area: Backwards compatibility hacks for proc macros A-proc-macros Area: Procedural macros C-future-incompatibility Category: Future-incompatibility lints C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#83583 opened Mar 27, 2021 by petrochenkov
12
Tracking Issue for proc_macro_back_compat A-proc-macro-back-compat Area: Backwards compatibility hacks for proc macros A-proc-macros Area: Procedural macros C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. S-tracking-needs-to-bake Status: The implementation is "complete" but it needs time to bake. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#83125 opened Mar 14, 2021 by Aaron1011
@Aaron1011
23
Remove NtIdent hack for regressed crates A-proc-macro-back-compat Area: Backwards compatibility hacks for proc macros A-proc-macros Area: Procedural macros C-future-incompatibility Category: Future-incompatibility lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#74616 opened Jul 22, 2020 by Aaron1011
1
5
Remove fn pretty_printing_compatibility_hack A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-pretty Area: Pretty printing (including `-Z unpretty`) A-proc-macro-back-compat Area: Backwards compatibility hacks for proc macros A-proc-macros Area: Procedural macros C-cleanup Category: PRs that clean code up or issues documenting cleanup. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#73933 opened Jul 1, 2020 by petrochenkov
5
ProTip! Follow long discussions with comments:>50.