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

9,905 Open 45,790 Closed
9,905 Open 45,790 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

Rust's i128 return ABI does not agree with Clang and GCC on Windows targets A-ABI Area: Concerning the application binary interface (ABI) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-windows Operating system: Windows T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134288 opened Dec 13, 2024 by tgross35
Tracking issue for release notes of #130766: Stabilize #[coverage] attribute A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134287 opened Dec 13, 2024 by rustbot
3 tasks
Cannot use unicode identifiers in --extern flags A-crates Area: Crates and their interactions (like crate loading) A-metadata Area: Crate metadata 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.
#134250 opened Dec 13, 2024 by Nemo157
5
ICE: not yet implemented: FIXME(async_closures): Lower these to SMIR A-stable-MIR Area: stable MIR C-bug Category: This is a bug. F-async_closure `#![feature(async_closure)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134246 opened Dec 13, 2024 by matthiaskrgr
1
@compiler-errors
7
The lack of safety requirements for some unsafe api documents in std 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.
#134242 opened Dec 13, 2024 by VaynNecol
10
Trivial bounds with associated types regression A-trait-system Area: Trait system C-bug Category: This is a bug. fixed-by-next-solver Fixed by the next-generation trait solver, `-Znext-solver`. P-low Low priority regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-types Relevant to the types team, which will review and decide on the PR/issue.
#134238 opened Dec 13, 2024 by konnorandrews
2
The combination of alloc_error_handler and target_features_11 is unsound C-bug Category: This is a bug. F-target_feature_11 target feature 1.1 RFC 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. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134234 opened Dec 12, 2024 by veluca93
bootstrap/compiletest: msys2 msys --skip filter behaves strangely A-compiletest Area: The compiletest test runner A-test-infra Area: test infrastructure (may span bootstrap/compiletest/more) C-enhancement Category: An issue proposing an enhancement or a PR with one. E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
#134226 opened Dec 12, 2024 by jieyouxu
1
alloc_error_handler can be an unsafe fn which is then unsoundly invoked C-bug Category: This is a bug. 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. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134225 opened Dec 12, 2024 by RalfJung
Adding a comment next to #![feature(ptr_metadata,)] silences failing doctests A-doctests Area: Documentation tests, run by rustdoc C-bug Category: This is a bug. I-prioritize Issue: Indicates that prioritization has been requested for this issue. regression-from-stable-to-stable Performance or correctness regression from one stable version to another. S-has-bisection Status: a bisection has been found for this issue S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#134221 opened Dec 12, 2024 by raldone01
1
10
SIGSEGV/SIGILL while building rustc itself in x86_64 apple CI jobs A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. CI-spurious-x86_64-apple-SIGSEGV-SIGILL CI spurious failure: SIGSEGV/SIGILL while building rustc itself on x86_64-apple I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. O-apple Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS) O-x86_64 Target: x86-64 processors (like x86_64-*) S-needs-repro Status: This issue has no reproduction and needs a reproduction to make progress. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134220 opened Dec 12, 2024 by jieyouxu
6
Detect different borrowing in different sub-expressions the same expression and suggest borrowing when applicable A-diagnostics Area: Messages for errors, warnings, and lints A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` D-terse Diagnostics: An error or lint that doesn't give enough information about the problem at hand. P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134219 opened Dec 12, 2024 by estebank
ICE: assertion failed: self.let_source != LetSource::None C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134217 opened Dec 12, 2024 by matthiaskrgr
1
Lint for returning a pointer to stack memory associated with a local variable 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.
#134215 opened Dec 12, 2024 by 1c3t3a
1
x test should support --show-output A-test-infra Area: test infrastructure (may span bootstrap/compiletest/more) C-enhancement Category: An issue proposing an enhancement or a PR with one. E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
#134210 opened Dec 12, 2024 by jyn514
-Zdump-mir introduces cycle in static containing static reference -Zdump-mir Unstable option: -Zdump-mir C-bug Category: This is a bug. I-cycle Issue: A query cycle occurred while none was expected 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.
#134205 opened Dec 12, 2024 by dtolnay
2
How much stack space should Windows reserve for stack overflow exceptions? A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-discussion Category: Discussion or questions that doesn't represent real issues. O-windows Operating system: Windows T-libs Relevant to the library team, which will review and decide on the PR/issue.
#134200 opened Dec 12, 2024 by ChrisDenton
3
./x test --skip is sensitive to path separators on Windows C-enhancement Category: An issue proposing an enhancement or a PR with one. O-windows Operating system: Windows T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
#134198 opened Dec 12, 2024 by ChrisDenton
1
compiletest: empty stderr if check-fail -> check-pass A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. E-needs-investigation Call for partcipation: This issues needs some investigation to determine current status T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
#134196 opened Dec 12, 2024 by jieyouxu
Invalid suggestion on anonymous lifetime parameter in precise capturing list if there are no input lifetimes A-diagnostics Area: Messages for errors, warnings, and lints A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` D-invalid-suggestion Diagnostics: A structured suggestion resulting in incorrect code. D-verbose Diagnostics: Too much output caused by a single piece of incorrect code. F-precise_capturing `#![feature(precise_capturing)]` P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134194 opened Dec 12, 2024 by fmease
unused_allocation lint produces incorrect suggestion for Box comparison A-diagnostics Area: Messages for errors, warnings, and lints A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. D-incorrect Diagnostics: A diagnostic that is giving misleading or incorrect information. L-unused_allocation Lint: unused_allocation T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134186 opened Dec 12, 2024 by arvidfm
Invalid suggestion for AsyncFnOnce trait object A-diagnostics Area: Messages for errors, warnings, and lints A-trait-objects Area: trait objects, vtable layout F-async_closure `#![feature(async_closure)]` T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#134182 opened Dec 11, 2024 by ehuss
@compiler-errors
1
ICE: Encountered error SignatureMismatch A-mir-opt-inlining Area: MIR inlining C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ 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.
#134174 opened Dec 11, 2024 by matthiaskrgr
@compiler-errors
9
Tracking Issue for rustdoc --doctest-compilation-args command line option C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#134172 opened Dec 11, 2024 by GuillaumeGomez
2 tasks
Incorrect Result reference in core::error. 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.
#134169 opened Dec 11, 2024 by bjoernager
1
4
ProTip! no:milestone will show everything without a milestone.