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,677 Open 44,781 Closed
9,677 Open 44,781 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

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 😕 57
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 😕 16
Tracking Issue for experimental yeet expressions (feature(yeet_expr)) C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#96373 opened Apr 25, 2022 by scottmcm
6 tasks
25 😕 11
Annotating higher-ranked lifetimes on closures is arduous A-closures Area: closures (`|args| { .. }`) A-lifetimes Area: lifetime related T-lang Relevant to the language team, which will review and decide on the PR/issue.
#58052 opened Feb 1, 2019 by pnkfelix
6 😕 6
Filter adapter for LendingIterator requires Polonius C-bug Category: This is a bug. F-generic_associated_types `#![feature(generic_associated_types)]` a.k.a. GATs fixed-by-polonius Compiling with `-Zpolonius` fixes this issue. GATs-triaged Issues using the `generic_associated_types` feature that have been triaged
#92985 opened Jan 16, 2022 by jackh726
3 😕 5
repr(Rust) unions (including MaybeUninit) do not preserve padding bytes T-opsem Relevant to the opsem team
#99604 opened Jul 22, 2022 by 5225225
10 😕 5
Tracking Issue for _ as a const argument: feature(generic_arg_infer) C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. F-generic_arg_infer Using `_` as a const argument: #![feature(generic_arg_infer)]`
#85077 opened May 8, 2021 by JulianKnodt
1 of 4 tasks
25 😕 5
Tracking Issue for stdio_makes_pipe 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.
#98288 opened Jun 20, 2022 by ChrisDenton
3 tasks
3 😕 4
Mutually exclusive traits still cause conflict in blancket implementation A-traits Area: Trait system 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.
#51774 opened Jun 25, 2018 by DominusCarnufex
3 😕 3
Conditional jumps equivalent to if(0 != 0) can appear in optimized assembly A-codegen Area: Code generation A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. E-needs-bisection Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc I-slow Issue: Problems and improvements with respect to performance of generated code. ICEBreaker-LLVM Bugs identified for the LLVM ICE-breaker group P-medium Medium priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#72343 opened May 19, 2020 by Diomendius
8 😕 3
Parse error recovery is obversable by macros in several cases A-diagnostics Area: Messages for errors, warnings, and lints A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-parser Area: The parsing of Rust source code to an AST. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#103534 opened Oct 25, 2022 by fmease
13 😕 3
The compiler looses vector capacity information A-codegen Area: Code generation A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. 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.
#82801 opened Mar 5, 2021 by MSxDOS
11 😕 3
Tracking Issue for De-RFC 3307: Remove type ascription 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-type_ascription `#![feature(type_ascription)]` S-tracking-remove-implementation Status: The feature needs to be removed from the Rust toolchain before this issue can be closed T-lang Relevant to the language team, which will review and decide on the PR/issue.
#101728 opened Sep 12, 2022 by Manishearth
2 of 7 tasks
@chenyukang
7 😕 3
where clause hides f64: Div<f64> impl A-traits Area: Trait system C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#89910 opened Oct 15, 2021 by m-ou-se
4 😕 3
Undefined reference to _Unwind_Resume A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#47493 opened Jan 16, 2018 by jefftime
18 😕 3
Tracking issue for future-incompatibility lint tyvar_behind_raw_pointer A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. 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.
#46906 opened Dec 21, 2017 by mikeyhew
22 😕 3
Tracking issue for RFC 3519: arbitrary_self_types 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-arbitrary_self_types `#![feature(arbitrary_self_types)]` S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. S-types-deferred Status: Identified as a valid potential future enhancement that is not currently being worked on 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.
#44874 opened Sep 26, 2017 by arielb1
1 of 9 tasks
129 😕 3
LLVM miscompiles large stack allocations 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
#100914 opened Aug 23, 2022 by Cl00e9ment
@wesleywiser
12 😕 3
Confusing lifetime error with closure A-closures Area: closures (`|args| { .. }`) A-lifetimes Area: lifetime related C-enhancement Category: An issue proposing an enhancement or a PR with one.
#42758 opened Jun 19, 2017 by dimbleby
6 😕 2
Check for Integer Overflow by Default 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.
#47739 opened Jan 25, 2018 by Apromixately
20 😕 2
Missed-optimization: extern "C" fn type calls are not nounwind A-ffi Area: Foreign Function Interface (FFI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. 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. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#64090 opened Sep 2, 2019 by gnzlbg
14 😕 2
Document guarantees (or lack thereof) regarding sign, quietness, and payload of NaNs A-floating-point Area: Floating point numbers and arithmetic A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. T-lang Relevant to the language team, which will review and decide on the PR/issue.
#73328 opened Jun 13, 2020 by ecstatic-morse
44 😕 2
LLVM can reorder rounding-mode-sensitive float operations outside rounding mode changes in SSE A-codegen Area: Code generation A-floating-point Area: Floating point numbers and arithmetic A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#72252 opened May 16, 2020 by pcwalton
5 😕 2
Tracking Issue for ops::Yeet (feature(try_trait_v2_yeet)) 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.
#96374 opened Apr 25, 2022 by scottmcm
4 tasks
13 😕 2
Rustdoc needs to handle conditional compilation somehow C-feature-request Category: A feature request, i.e: not implemented / a PR. E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. P-low Low priority T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#1998 opened Mar 16, 2012 by brson
34 😕 2
ProTip! Updated in the last three days: updated:>2024-09-19.