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,825 Open 45,392 Closed
9,825 Open 45,392 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

The run-make/version-verbose-commit-hash test doesn't reliably detect when the commit hash is missing A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
#132875 opened Nov 10, 2024 by RalfJung
False positive dead_code lint when type is only used via destructuring 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.
#132874 opened Nov 10, 2024 by daniel5151
[rustc 1.84.0-nightly (59cec72a5 2024-11-08)]: unknown unstable option: profile C-discussion Category: Discussion or questions that doesn't represent real issues. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132868 opened Nov 10, 2024 by yngrtc
1
./x clippy errors if lint levels are passed as multiple arguments C-bug Category: This is a bug. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
#132867 opened Nov 10, 2024 by lolbinarycat
1
Support calling functions with SIMD vectors that couldn't be used in the caller 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. A-SIMD Area: SIMD (Single Instruction Multiple Data) C-feature-request Category: A feature request, i.e: not implemented / a PR. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. T-opsem Relevant to the opsem team WG-llvm Working group: LLVM backend code generation
#132865 opened Nov 10, 2024 by RalfJung
rust_2024_prelude_collisions fails with glob of underscore import A-edition-2024 Area: The 2024 edition C-bug Category: This is a bug. D-edition Diagnostics: An error or lint that should account for edition differences. D-invalid-suggestion Diagnostics: A structured suggestion resulting in incorrect code. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged.
#132864 opened Nov 10, 2024 by ehuss
ICE when compiling a source file with size 4 GiB - 1 B 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.
#132862 opened Nov 10, 2024 by tyilo
1
Possible false-negative with tail-expr-drop-order A-edition-2024 Area: The 2024 edition A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. C-bug Category: This is a bug. D-edition Diagnostics: An error or lint that should account for edition differences. F-shorter_tail_lifetimes `#![feature(shorter_tail_lifetimes)]` L-false-negative Lint: False negative (should have fired but didn't). needs-triage This issue may need triage. Remove it if it has been sufficiently triaged.
#132861 opened Nov 10, 2024 by ehuss
@dingxiangfei2009
2
The diagnostic emitter doesn't deal with non-ASCII characters correctly when eliding parts of overly long source lines A-diagnostics Area: Messages for errors, warnings, and lints A-Unicode Area: Unicode C-bug Category: This is a bug. D-diagnostic-infra Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself. P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132860 opened Nov 10, 2024 by fmease
@fmease
1
Tracking issue for release notes of #132577: Report the unexpected_cfgs lint in external macros L-unexpected_cfgs Lint: unexpected_cfgs 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.
#132859 opened Nov 10, 2024 by rustbot
1 of 3 tasks
unsafe_op_in_unsafe_fn causes unnecessary unsafe warnings A-diagnostics Area: Messages for errors, warnings, and lints A-edition-2024 Area: The 2024 edition A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` D-edition Diagnostics: An error or lint that should account for edition differences. D-papercut Diagnostics: An error or lint that needs small tweaks. L-false-positive Lint: False positive (should not have fired). L-unsafe_op_in_unsafe_fn Lint: unsafe_op_in_unsafe_fn T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132856 opened Nov 10, 2024 by ehuss
Tracking issue for release notes of #131080: Stabilize WebAssembly multivalue, reference-types, and tail-call target features O-wasm Target: WASM (WebAssembly), http://webassembly.org/ 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.
#132855 opened Nov 10, 2024 by rustbot
3 tasks
2024 impl_trait_overcaptures ambiguous + A-diagnostics Area: Messages for errors, warnings, and lints A-edition-2024 Area: The 2024 edition A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` D-edition Diagnostics: An error or lint that should account for edition differences. D-invalid-suggestion Diagnostics: A structured suggestion resulting in incorrect code. L-impl_trait_overcaptures Lint: impl_trait_overcaptures T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132853 opened Nov 10, 2024 by ehuss
All interrupt ABIs should enforce either () or ! as return types A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. F-abi_x86_interrupt O-msp430 O-riscv Target: RISC-V architecture O-x86_32 Target: x86 processors, 32 bit (like i686-*) O-x86_64 Target: x86-64 processors (like x86_64-*) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132841 opened Nov 10, 2024 by workingjubilee
Directly calling "msp430-interrupt" fn should also be invalid A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-msp430 T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132839 opened Nov 10, 2024 by workingjubilee
nightly-2024-11-10 is unavailable C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
#132838 opened Nov 10, 2024 by taiki-e
Most extern "*-interrupt-*" fn should enforce 0-sized signatures A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-msp430 O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132837 opened Nov 10, 2024 by workingjubilee
3
Directly calling extern "riscv-interrupt-{m,s}" fn... compiles? A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132836 opened Nov 10, 2024 by workingjubilee
6
extern "x86-interrupt" fn allows absurd signatures A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. F-abi_x86_interrupt O-x86_32 Target: x86 processors, 32 bit (like i686-*) O-x86_64 Target: x86-64 processors (like x86_64-*) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132835 opened Nov 10, 2024 by workingjubilee
Directly calling "x86-interrupt" fn should be invalid A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. F-abi_x86_interrupt O-x86_32 Target: x86 processors, 32 bit (like i686-*) O-x86_64 Target: x86-64 processors (like x86_64-*) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132834 opened Nov 10, 2024 by workingjubilee
Using a trait's Associated Type in a different trait's impl declaration crashes 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.
#132826 opened Nov 9, 2024 by poday
1
ICE: assertion failed: !obligation.predicate.has_escaping_bound_vars() C-bug Category: This is a bug. F-non_lifetime_binders `#![feature(non_lifetime_binders)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ requires-debug-assertions This issue requires a build of rustc or tooling with debug-assertions in some way T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132822 opened Nov 9, 2024 by matthiaskrgr
2
rust_2024_incompatible_pat does not work with macros A-diagnostics Area: Messages for errors, warnings, and lints A-edition-2024 Area: The 2024 edition A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-suggestion-diagnostics Area: Suggestions generated by the compiler applied by `cargo fix` D-edition Diagnostics: An error or lint that should account for edition differences. L-rust_2024_incompatible_pat Lint: rust_2024_incompatible_pat T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132821 opened Nov 9, 2024 by ehuss
2024 No migration for a particular RPIT scenario (async?) A-edition-2024 Area: The 2024 edition C-bug Category: This is a bug. D-edition Diagnostics: An error or lint that should account for edition differences. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132819 opened Nov 9, 2024 by ehuss
1
3
Tracking Issue for io_slice_as_bytes 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.
#132818 opened Nov 9, 2024 by aDotInTheVoid
1 of 4 tasks
ProTip! no:milestone will show everything without a milestone.