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.

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
2,187 Open 4,816 Closed
2,187 Open 4,816 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
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Emit a warning when gold is used as the linker A-diagnostics Area: Messages for errors, warnings, and lints A-linkers Area: linkers... you gotta love linkers C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141748 opened May 29, 2025 by Noratrieb
1
2
type annotations needed for if let Some(whatever) = todo!() { not very helpful A-diagnostics Area: Messages for errors, warnings, and lints A-patterns Relating to patterns and pattern matching T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141742 opened May 29, 2025 by matthiaskrgr
3
error message for inherent impl on type that is external could be more explanatory A-diagnostics Area: Messages for errors, warnings, and lints 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.
#141679 opened May 28, 2025 by cyrgani
track the version and PR in which a nightly feature was removed A-diagnostics Area: Messages for errors, warnings, and lints E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. E-help-wanted Call for participation: Help is requested to fix this issue. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141619 opened May 26, 2025 by jyn514
1
@xizheyin
5
track renamed and removed library feature gates A-diagnostics Area: Messages for errors, warnings, and lints A-stability Area: `#[stable]`, `#[unstable]` etc. C-feature-request Category: A feature request, i.e: not implemented / a PR. E-help-wanted Call for participation: Help is requested to fix this issue. E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate. E-mentor Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion. F-staged_api `#![feature(staged_api)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#141617 opened May 26, 2025 by jyn514
3
unused_assignment triggered by closure even though value is used A-closures Area: Closures (`|…| { … }`) A-diagnostics Area: Messages for errors, warnings, and lints A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. D-imprecise-spans Diagnostics: spans don't point to exactly the erroneous code L-unused_assignments Lint: unused_assignments T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141615 opened May 26, 2025 by y86-dev
4
Confusing diagnostic when trying to invoke a macro in a module A-decl-macros-1-2 Area: Declarative macros 1.2 A-diagnostics Area: Messages for errors, warnings, and lints D-lack-of-suggestion Diagnostics: Adding a (structured) suggestion would increase the quality of the diagnostic. 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.
#141613 opened May 26, 2025 by BigWingBeat
Forgetting a right angle bracket (>) gives: "error: Fn traits cannot take lifetime parameters" A-diagnostics Area: Messages for errors, warnings, and lints A-parser Area: The lexing & parsing of Rust source code to an AST D-confusing Diagnostics: Confusing error or lint that should be reworked. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141436 opened May 23, 2025 by theemathas
3
Confusing error message from a missing comma A-diagnostics Area: Messages for errors, warnings, and lints A-parser Area: The lexing & parsing of Rust source code to an AST D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141403 opened May 22, 2025 by pacak
2
Diagnostic assumes that braced unresolved identifiers are formatting arguments A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name/path resolution done by `rustc_resolve` specifically D-incorrect Diagnostics: A diagnostic that is giving misleading or incorrect information. D-papercut Diagnostics: An error or lint that needs small tweaks. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141350 opened May 21, 2025 by fmease
1
@xizheyin
8
type inference failure confusing diagnostic let Some(x) = None for [u8] A-diagnostics Area: Messages for errors, warnings, and lints A-inference Area: Type inference D-confusing Diagnostics: Confusing error or lint that should be reworked. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141336 opened May 21, 2025 by midnightveil
8
Identify which tuple item fails to implement a trait when using fake variadics A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141258 opened May 19, 2025 by alice-i-cecile
1
Suboptimal diagnostic for Cow<'static, [SomeType]> if SomeType doesn't implement Clone A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141241 opened May 19, 2025 by weiznich
wrong span for E0277 A-diagnostics Area: Messages for errors, warnings, and lints D-confusing Diagnostics: Confusing error or lint that should be reworked. D-imprecise-spans Diagnostics: spans don't point to exactly the erroneous code D-incorrect Diagnostics: A diagnostic that is giving misleading or incorrect information. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141234 opened May 18, 2025 by jendrikw
1
Nested import suggestion should maintain the same visibility level A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141134 opened May 17, 2025 by bvanjoi
rustdoc: terse diagnostic on malformed intra-doc link (single instead of double colon) A-diagnostics Area: Messages for errors, warnings, and lints A-intra-doc-links Area: Intra-doc links, the ability to link to items in docs by name C-feature-request Category: A feature request, i.e: not implemented / a PR. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#141095 opened May 16, 2025 by sanbox-irl
1
Confusing error when using non-XID_Start characters in lifetime names A-diagnostics Area: Messages for errors, warnings, and lints A-lexer Area: lexer T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141081 opened May 16, 2025 by jieyouxu
@mu001999
1
Mutex and RwLock borrow suggestions could suggest get_mut if applicable A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141058 opened May 15, 2025 by zopsicle
refining_impl_trait: The suggested fix does not yet take precise capturing into account. A-diagnostics Area: Messages for errors, warnings, and lints A-impl-trait Area: `impl Trait`. Universally / existentially quantified anonymous types with static dispatch. A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. D-invalid-suggestion Diagnostics: A structured suggestion resulting in incorrect code. L-refining_impl_trait Lint group: refining_impl_trait T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#141047 opened May 15, 2025 by Tamschi
Typoing "." instead of "," in a match produces confusing error messages A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140991 opened May 14, 2025 by ssbr
1
@chenyukang
4
Early/late bound lifetime coercion produces a confusing diagnostic A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140896 opened May 10, 2025 by parrottq
Misleading "captured variable cannot escape FnMut closure body" diagnostic, should be "can't mutable borrow more than once" A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140875 opened May 9, 2025 by teor2345
Confusing diagnostics when forgetting to import rustc_abi crate A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140840 opened May 9, 2025 by RalfJung
4
"[E0603] unit variant X is private. help: import X directly" suggests invalid path in private module A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name/path resolution done by `rustc_resolve` specifically A-visibility Area: Visibility / privacy D-invalid-suggestion Diagnostics: A structured suggestion resulting in incorrect code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140831 opened May 8, 2025 by ZaneErebos
@xizheyin
1
Polymorphic recursion in async fn gives "queries overflow the depth limit" error A-async-await Area: Async & Await A-diagnostics Area: Messages for errors, warnings, and lints C-bug Category: This is a bug. I-cycle Issue: A query cycle occurred while none was expected T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#140728 opened May 7, 2025 by theemathas
ProTip! What’s not been updated in a month: updated:<2025-04-29.