Skip to content

Issues: rust-lang/rust

Draft release notes for 1.87
#140133 opened Apr 21, 2025 by BoxyUwU
Open 3
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
38 Open 99 Closed
38 Open 99 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

u16 format precision change, breach of the Rust stability guarantee A-fmt Area: `core::fmt` A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. I-libs-api-nominated Nominated for discussion during a libs-api team meeting. I-prioritize Issue: Indicates that prioritization has been requested for this issue. regression-untriaged Untriaged performance or correctness regression. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#140250 opened Apr 24, 2025 by ijackson
4
add an internal lint for nightly-channel-only features without a feature gate A-lints Area: Lints (warnings about flaws in source code) such as unused_mut. A-stability Area: `#[stable]`, `#[unstable]` etc. 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.
#139892 opened Apr 16, 2025 by jyn514
6
-Z allow-features does not apply to -Z flags A-CLI Area: Command-line interface (CLI) to the compiler A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#139890 opened Apr 16, 2025 by jyn514
1
Document path stability of f64::abs in no std crates A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-stability Area: `#[stable]`, `#[unstable]` etc. C-enhancement Category: An issue proposing an enhancement or a PR with one. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#139066 opened Mar 28, 2025 by lopopolo
2
Built-in attributes are treated differently vs prelude attributes, unstable built-in attributes can name-collide with stable macro, and built-in attributes can break back-compat A-attributes Area: Attributes (`#[…]`, `#![…]`) A-resolve Area: Name/path resolution done by `rustc_resolve` specifically A-stability Area: `#[stable]`, `#[unstable]` etc. C-discussion Category: Discussion or questions that doesn't represent real issues. I-lang-radar Items that are on lang's radar and will need eventual work or consideration. 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.
#134963 opened Dec 31, 2024 by jieyouxu
3
Nightly-only cfg gating like #[cfg(target_has_atomic)] is confusing A-cfg Area: `cfg` conditional compilation A-stability Area: `#[stable]`, `#[unstable]` etc. C-enhancement Category: An issue proposing an enhancement or a PR with one. requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133295 opened Nov 21, 2024 by jieyouxu
11
std::arch::wasm::unreachable() is stable but does not compile A-diagnostics Area: Messages for errors, warnings, and lints A-stability Area: `#[stable]`, `#[unstable]` etc. D-imprecise-spans Diagnostics: spans don't point to exactly the erroneous code D-papercut Diagnostics: An error or lint that needs small tweaks. O-wasm Target: WASM (WebAssembly), http://webassembly.org/
#133015 opened Nov 13, 2024 by eric-seppanen
9
Recursive const stability checks do not apply in const items A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-const-eval Working group: Const evaluation
#132536 opened Nov 2, 2024 by RalfJung
2
ICE in check_mod_const_bodies when compiling a modified libcore A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. F-rustc_attrs Internal rustc attributes gated on the `#[rustc_attrs]` feature gate. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ P-low Low priority requires-internal-features This issue requires the use of internal features. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#122948 opened Mar 23, 2024 by mzabaluev
4
CI accepted doctests that do not build (due to missing feature gates) A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#114838 opened Aug 15, 2023 by RalfJung
12
Don't suggest feature-gated paths on stable A-diagnostics Area: Messages for errors, warnings, and lints A-stability Area: `#[stable]`, `#[unstable]` etc. 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.
#101956 opened Sep 17, 2022 by QuineDot
1
Allow multiple #[unstable] attributes on one item 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. F-staged_api `#![feature(staged_api)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#94770 opened Mar 9, 2022 by m-ou-se
2
@dianne
3
const-features can be both stable and unstable at the same time A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#91357 opened Nov 29, 2021 by RalfJung
Surprising missing stability attribute error A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug.
#84935 opened May 5, 2021 by illicitonion
2
Rustc should warn if you have a stability attribute on a non-public item A-contributor-roadblock Area: Makes things more difficult for new or seasoned contributors to Rust A-stability Area: `#[stable]`, `#[unstable]` etc. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#83380 opened Mar 22, 2021 by jyn514
1
3
Forbid #[rustc_const_stable] without #[stable] A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-stability Area: `#[stable]`, `#[unstable]` etc. C-enhancement Category: An issue proposing an enhancement or a PR with one. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#79551 opened Nov 30, 2020 by CraftSpider
1
13
Stability annotation on defaulted generics fails A-allocators Area: Custom and system allocators A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#79499 opened Nov 28, 2020 by TimDiekmann
3
Rust suggests unstable paths for non-imported item A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name/path resolution done by `rustc_resolve` specifically A-stability Area: `#[stable]`, `#[unstable]` etc. A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` C-enhancement Category: An issue proposing an enhancement or a PR with one. D-confusing Diagnostics: Confusing error or lint that should be reworked. D-papercut Diagnostics: An error or lint that needs small tweaks. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#78130 opened Oct 20, 2020 by carbotaniuman
1
rustc --print unstable-features A-stability Area: `#[stable]`, `#[unstable]` etc. 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.
#77937 opened Oct 14, 2020 by lnicola
1
Feature gate for unstable target_feature values not being checked on nightly A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. requires-nightly This issue requires a nightly compiler in some way. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#76842 opened Sep 17, 2020 by mystor
2
De-stabilize target spec JSON A-stability Area: `#[stable]`, `#[unstable]` etc. A-target-specs Area: Compile-target specifications T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#71009 opened Apr 10, 2020 by Mark-Simulacrum
21
Initializers of stable constants can call const unstable functions A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#68743 opened Feb 1, 2020 by ecstatic-morse
4
Reduce the places where stable annotations are needed A-stability Area: `#[stable]`, `#[unstable]` etc. C-enhancement Category: An issue proposing an enhancement or a PR with one. F-staged_api `#![feature(staged_api)]` P-medium Medium priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#65515 opened Oct 17, 2019 by estebank
1
@estebank
18
The never type can be named despite its feature gate A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#58733 opened Feb 25, 2019 by SimonSapin
8
libcore can use unstable library features without a feature flag A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#58705 opened Feb 24, 2019 by RalfJung
ProTip! Find all open issues with in progress development work with linked:pr.