Skip to content

Issues: rust-lang/rust

Draft release notes for 1.88.0
#141598 opened May 26, 2025 by Mark-Simulacrum
Open 9
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

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
Assigned to nobody Loading
Sort

Issues list

Permit attributes on use items A-attributes Area: Attributes (`#[…]`, `#![…]`) A-grammar Area: The grammar of Rust A-resolve Area: Name/path resolution done by `rustc_resolve` specifically C-feature-request Category: A feature request, i.e: not implemented / a PR. I-lang-nominated Nominated for discussion during a lang team meeting. P-lang-drag-2 Lang team prioritization drag level 2.https://rust-lang.zulipchat.com/#narrow/channel/410516-t-lang. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#141704 opened May 28, 2025 by jhpratt
impl blocks do not support conditional type parameters A-attributes Area: Attributes (`#[…]`, `#![…]`) A-cfg Area: `cfg` conditional compilation A-grammar Area: The grammar of Rust C-feature-request Category: A feature request, i.e: not implemented / a PR. needs-rfc This change is large or controversial enough that it should have an RFC accepted before doing it. 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. T-types Relevant to the types team, which will review and decide on the PR/issue.
#119281 opened Dec 24, 2023 by andreisilviudragnea
Ranges of match expressions incorrectly parsed A-grammar Area: The grammar of Rust C-bug Category: This is a bug.
#112329 opened Jun 5, 2023 by clarfonthey
Allow numeric tokens containing 'e' that aren't exponents be passed to proc macros A-grammar Area: The grammar of Rust A-proc-macros Area: Procedural macros C-feature-request Category: A feature request, i.e: not implemented / a PR. I-lang-easy-decision Issue: The decision needed by the team is conjectured to be easy; this does not imply nomination 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.
#111615 opened May 15, 2023 by ogoffart
Unable to Utilize unsafe {} Blocks as an Expression A-diagnostics Area: Messages for errors, warnings, and lints A-grammar Area: The grammar of Rust A-parser Area: The lexing & parsing of Rust source code to an AST D-terse Diagnostics: An error or lint that doesn't give enough information about the problem at hand. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#98093 opened Jun 14, 2022 by HTGAzureX1212
Bug when mixing /**/ and // comments on * operator A-grammar Area: The grammar of Rust C-discussion Category: Discussion or questions that doesn't represent real issues. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#82997 opened Mar 11, 2021 by ALRBP
Creating a macro of generating closure, description of arguments to closure in || with a star only works as an exclamation point. A-grammar Area: The grammar of Rust A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-parser Area: The lexing & parsing of Rust source code to an AST C-feature-request Category: A feature request, i.e: not implemented / a PR. 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.
#72652 opened May 27, 2020 by denisandroid
Failure to parse {2} + {2} A-grammar Area: The grammar of Rust A-parser Area: The lexing & parsing of Rust source code to an AST C-discussion Category: Discussion or questions that doesn't represent real issues. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#54482 opened Sep 22, 2018 by blaztinn
Operators in patterns have incorrect priorities A-grammar Area: The grammar of Rust A-parser Area: The lexing & parsing of Rust source code to an AST A-patterns Relating to patterns and pattern matching C-enhancement Category: An issue proposing an enhancement or a PR with one. F-exclusive_range_pattern `#![feature(exclusive_range_pattern)]` F-half_open_range_patterns `#![feature(half_open_range_patterns)]` 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.
#48501 opened Feb 24, 2018 by petrochenkov
Grammar ambiguity with left shifts and fully qualified (UFCS) paths A-grammar Area: The grammar of Rust A-parser Area: The lexing & parsing of Rust source code to an AST C-enhancement Category: An issue proposing an enhancement or a PR with one. P-low Low priority T-lang Relevant to the language team, which will review and decide on the PR/issue.
#45144 opened Oct 9, 2017 by petrochenkov
Range expressions: discrepancies between rustc and parser-lalr A-grammar Area: The grammar of Rust C-bug Category: This is a bug. I-needs-decision Issue: In need of a decision. P-medium Medium priority T-lang Relevant to the language team, which will review and decide on the PR/issue.
#28785 opened Oct 1, 2015 by rprichard
Use of ty macro non-terminal in trait bounds A-grammar Area: The grammar of Rust C-feature-request Category: A feature request, i.e: not implemented / a PR. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#20272 opened Dec 28, 2014 by stuglaser
Tracking issue for stmt_expr_attributes: Add attributes to expressions, etc. A-grammar Area: The grammar of Rust B-RFC-implemented Blocker: Approved by a merged RFC and implemented but not stabilized. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC F-stmt_expr_attributes `#![feature(stmt_expr_attributes)]` S-tracking-design-concerns Status: There are blocking design concerns. S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#15701 opened Jul 15, 2014 by brson
1 of 5 tasks
ProTip! Updated in the last three days: updated:>2025-05-28.