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
77 Open 177 Closed
77 Open 177 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

Some unused_parens suggestions can result in keyword soup (even if technically correct). A-control-flow Area: Relating to control flow A-diagnostics Area: Messages for errors, warnings, and lints A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. L-unused_parens Lint: unused_parens T-lang Relevant to the language team, which will review and decide on the PR/issue.
#114161 opened Jul 28, 2023 by eddyb
Codegen backends should validate their assumed encodings of e.g. rustc layouts. A-codegen Area: Code generation A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#105282 opened Dec 5, 2022 by eddyb
3
Consider uploading RA LSIF data to sourcegraph, from bors builds. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
#101446 opened Sep 5, 2022 by eddyb
13
Redundant error for "implementation ... not general enough" in "NLL" mode / since 1.63 (when it was made permanent). A-borrow-checker Area: The borrow checker A-diagnostics Area: Messages for errors, warnings, and lints A-lifetimes Area: lifetime related 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.
#100742 opened Aug 19, 2022 by eddyb
4
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
Transmute special-case doesn't take into consideration alignment or enum repr. A-layout Area: Memory layout of types C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#88290 opened Aug 24, 2021 by eddyb
2
v0 mangling should avoid backrefs when they're not shorter than their target. A-linkage Area: linking into static, shared libraries and binaries C-enhancement Category: An issue proposing an enhancement or a PR with one. I-heavy Issue: Problems and improvements with respect to binary size of generated code.
#87511 opened Jul 27, 2021 by eddyb
2
global_asm! does not register location information to LLVM, resulting in suboptimal error reporting. A-diagnostics Area: Messages for errors, warnings, and lints A-inline-assembly Area: inline asm!(..) 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. 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.
#81751 opened Feb 4, 2021 by eddyb
1
#[rustc_inherit_overflow_checks] should be documented instead of replaced with e.g. Add::add calls. A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools T-libs Relevant to the library team, which will review and decide on the PR/issue.
#81721 opened Feb 3, 2021 by eddyb
4
Consider providing an universal way to read (proc macro) dylib metadata. A-codegen Area: Code generation A-metadata Area: Crate metadata A-proc-macros Area: Procedural macros T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#79239 opened Nov 20, 2020 by eddyb
1
Cycle error through variance computation when using -> _. A-inference Area: Type inference C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#72730 opened May 29, 2020 by eddyb
6
Closure signature hinting doesn't elaborate bounds. A-closures Area: closures (`|args| { .. }`) A-inference Area: Type inference 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.
#71713 opened Apr 30, 2020 by eddyb
2
"constant expression depends on a generic parameter" error can be improved. A-const-eval Area: constant evaluation (mir interpretation) A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. PG-const-generics Project group: Const generics T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#71142 opened Apr 14, 2020 by eddyb
ICEs + RUST_BACKTRACE=1 should interleave the backtrace and query stack. A-diagnostics Area: Messages for errors, warnings, and lints 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.
#70954 opened Apr 9, 2020 by eddyb
Wasteful duplication between incremental build dirs and normal artifacts. A-incr-comp Area: Incremental compilation C-enhancement Category: An issue proposing an enhancement or a PR with one. I-heavy Issue: Problems and improvements with respect to binary size of generated code. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#70823 opened Apr 5, 2020 by eddyb
Consider renaming (Re)EarlyBound to ReParam and (Re)LateBound to Bound. A-lifetimes Area: lifetime related A-typesystem Area: The type system C-cleanup Category: PRs that clean code up or issues documenting cleanup. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#70805 opened Apr 5, 2020 by eddyb
1
rustdoc's treatment of cross-crate ("imported") files is suboptimal. C-enhancement Category: An issue proposing an enhancement or a PR with one. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#70757 opened Apr 4, 2020 by eddyb
@ollie27
4
rustc_mir::shim misuses ParamEnvs. A-mir Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#70520 opened Mar 29, 2020 by eddyb
CI logs should be split by build steps, or stages at the very least. C-enhancement Category: An issue proposing an enhancement or a PR with one. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
#70472 opened Mar 27, 2020 by eddyb
4
ninja is only used in Windows builds on CI. 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. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
#70469 opened Mar 27, 2020 by eddyb
Move from {{closure}}#0 syntax to {closure#0} for (def) path components. A-mir Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html C-cleanup Category: PRs that clean code up or issues documenting cleanup. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#70334 opened Mar 23, 2020 by eddyb
5
Consider printing the query stack on ICE, even without RUST_BACKTRACE. 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.
#70287 opened Mar 22, 2020 by eddyb
rustc_span footgun: ensure_source_file_source_present has to be manually called. C-cleanup Category: PRs that clean code up or issues documenting cleanup. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#69739 opened Mar 5, 2020 by eddyb
We should use crate visibility in implementation details like std::sys. A-visibility Area: Visibility / privacy. 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.
#69737 opened Mar 5, 2020 by eddyb
4
MIR SourceScopes stay around even when all their uses were removed. A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) A-mir Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html C-enhancement Category: An issue proposing an enhancement or a PR with one. P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#68964 opened Feb 8, 2020 by eddyb
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.