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
9,593 Open 44,583 Closed
9,593 Open 44,583 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

Tracking issue for specialization (RFC 1210) A-specialization Area: Trait impl specialization A-traits Area: Trait system B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-RFC-implemented Blocker: Approved by a merged RFC and implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-specialization `#![feature(specialization)]` I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness requires-nightly This issue requires a nightly compiler in some way. S-tracking-design-concerns Status: There are blocking ❌ design concerns. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#31844 opened Feb 23, 2016 by nikomatsakis
1 of 8 tasks
317 👀 71
Miscompilation: Equal pointers comparing as unequal A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-llvm Working group: LLVM backend code generation
#107975 opened Feb 13, 2023 by JakobDegen
97 👀 60
Tracking issue: declarative macros 2.0 A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-decl_macro `#![feature(decl_macro)]` S-tracking-design-concerns Status: There are blocking ❌ design concerns. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#39412 opened Jan 30, 2017 by nrc
11 of 19 tasks
75 👀 43
Implied bounds on nested references + variance = soundness hole A-typesystem Area: The type system A-variance Area: Variance (https://doc.rust-lang.org/nomicon/subtyping.html) C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-medium Medium priority S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. T-types Relevant to the types team, which will review and decide on the PR/issue.
#25860 opened May 28, 2015 by aturon
56 👀 34
Tracking Issue for strict_provenance A-strict-provenance Area: Strict provenance for raw pointers C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#95228 opened Mar 23, 2022 by Gankra
1 of 13 tasks
161 👀 34
&& operator chains (and ||, possibly) generates unoptimizable LLVM IR A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-enhancement Category: An issue proposing an enhancement or a PR with one. C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such I-slow Issue: Problems and improvements with respect to performance of generated code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#83623 opened Mar 28, 2021 by AngelicosPhosphoros
21 👀 31
Tracking issue for ? operator and try blocks (RFC 243, question_mark & try_blocks features) A-error-handling Area: Error handling B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-RFC-implemented Blocker: Approved by a merged RFC and implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-try_blocks `#![feature(try_blocks)]` Libs-Tracked Libs issues that are tracked on the team's project board. S-tracking-design-concerns Status: There are blocking ❌ design concerns. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#31436 opened Feb 5, 2016 by nikomatsakis
10 of 12 tasks
448 👀 29
Tracking issue for #![feature(async_closure)] (RFC 2394 / RFC 3668) A-async-await Area: Async & Await A-closures Area: closures (`|args| { .. }`) AsyncAwait-Triaged Async-await issues that have been triaged during a working group meeting. B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-RFC-implemented Blocker: Approved by a merged RFC and implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-async_closure `#![feature(async_closure)]` requires-nightly This issue requires a nightly compiler in some way. 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. WG-async Working group: Async & await
#62290 opened Jul 2, 2019 by Centril
4 of 7 tasks
35 👀 27
Tracking issue for WebAssembly atomics C-discussion Category: Discussion or questions that doesn't represent real issues. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. O-wasm Target: WASM (WebAssembly), http://webassembly.org/
#77839 opened Oct 12, 2020 by alexcrichton
15 👀 25
Tracking issue for trait aliases A-traits Area: Trait system B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-trait_alias `#![feature(trait_alias)]` 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.
#41517 opened Apr 24, 2017 by withoutboats
5 of 13 tasks
114 👀 25
Missing caching for HRTB projection equality bounds (for<'x> T: Trait<'x, Assoc = ...>). A-associated-items Area: Associated items such as associated types and consts. A-traits Area: Trait system I-compiletime Issue: Problems and improvements with respect to compile times. T-compiler Relevant to the compiler 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.
#99188 opened Jul 12, 2022 by eddyb
19 👀 24
Tracking issue: deref patterns A-patterns Relating to patterns and pattern matching C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-deref_patterns `#![feature(deref_patterns)]` needs-rfc This change is large or controversial enough that it should have an RFC accepted before doing it. S-tracking-design-concerns Status: There are blocking ❌ design concerns. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#87121 opened Jul 14, 2021 by nrc
1 of 6 tasks
66 👀 23
Tracking Issue for f16 and f128 float types B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` 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.
#116909 opened Oct 18, 2023 by traviscross
32 of 82 tasks
@tgross35
28 👀 23
Tracking Issue for complex generic constants: feature(generic_const_exprs) A-const-generics Area: const generics (parameters and arguments) C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-generic_const_exprs `#![feature(generic_const_exprs)]` S-tracking-impl-incomplete Status: The implementation is incomplete. 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.
#76560 opened Sep 10, 2020 by lcnr
64 👀 14
Coherence can be bypassed by an indirect impl for a trait object A-dst Area: Dynamically Sized Types A-traits Area: Trait system C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. 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.
#57893 opened Jan 25, 2019 by arielb1
60 👀 13
Tracking issue for step_trait stabilization A-iterators Area: Iterators B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. Libs-Tracked Libs issues that are tracked on the team's project board. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#42168 opened May 23, 2017 by scottmcm
4 tasks
55 👀 13
Tracking issue for Fn traits (unboxed_closures & fn_traits feature) B-RFC-implemented Blocker: Approved by a merged RFC and implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-unboxed_closures `#![feature(unboxed_closures)]` S-tracking-design-concerns Status: There are blocking ❌ design concerns. T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#29625 opened Nov 5, 2015 by aturon
1 of 2 tasks
66 👀 13
Allocator traits and std::heap A-allocators Area: Custom and system allocators B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. Libs-Tracked Libs issues that are tracked on the team's project board. 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. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#32838 opened Apr 8, 2016 by nikomatsakis
6 of 12 tasks
470 👀 13
Meta tracking issue for const fn A-attributes Area: #[attributes(..)] A-const-eval Area: constant evaluation (mir interpretation) A-const-fn Area: const fn foo(..) {..}. Pure functions which can be applied at compile time. A-diagnostics Area: Messages for errors, warnings, and lints A-stability Area: issues related to #[stable] and #[unstable] attributes themselves. metabug Issues about issues themselves ("bugs about bugs") 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.
#57563 opened Jan 13, 2019 by Lokathor
12 of 25 tasks
95 👀 12
Tracking issue for eRFC 2497, "if- and while-let-chains, take 2" B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-let_chains `#![feature(let_chains)]` S-tracking-ready-to-stabilize Status: This is ready to stabilize; it may need a stabilization report and a PR T-lang Relevant to the language team, which will review and decide on the PR/issue.
#53667 opened Aug 24, 2018 by Centril
8 of 14 tasks
1
68 👀 12
Tracking Issue for -Znext-solver A-traits Area: Trait system C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-types Relevant to the types team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative
#107374 opened Jan 27, 2023 by lcnr
6 of 11 tasks
2 👀 11
Tracking issue for RFC 2294, "if let guard" B-RFC-implemented Blocker: Approved by a merged RFC and implemented. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-if_let_guard `#![feature(if_let_guard)]` S-tracking-impl-incomplete Status: The implementation is incomplete. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#51114 opened May 27, 2018 by Centril
1 of 8 tasks
28 👀 10
'static closures/FnDefs/futures with non-'static return type are unsound A-associated-items Area: Associated items such as associated types and consts. A-async-await Area: Async & Await A-closures Area: closures (`|args| { .. }`) A-lifetimes Area: lifetime related A-traits Area: Trait system A-typesystem Area: The type system AsyncAwait-Triaged Async-await issues that have been triaged during a working group meeting. C-bug Category: This is a bug. I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness P-high High priority S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. 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.
#84366 opened Apr 20, 2021 by steffahn
1
10 👀 9
Tracking Issue for std::cell::{Ref, RefMut}::leak B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. Libs-Tracked Libs issues that are tracked on the team's project board. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
#69099 opened Feb 12, 2020 by HeroicKatora
3 tasks
4 👀 8
Inlined function duplication across complex branches when extern "Rust" is used with LTO and opt-level="s" A-lto Area: Link Time Optimization I-heavy Issue: Problems and improvements with respect to binary size of generated code. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state O-msp430 T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#102295 opened Sep 26, 2022 by cr1901
👀 8
ProTip! Updated in the last three days: updated:>2024-09-02.