Skip to content

Issues: rust-lang/rust

Draft release notes for 1.87
#140133 opened Apr 21, 2025 by BoxyUwU
Open 3
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
142 Open 685 Closed
142 Open 685 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

LazyLock not working as expected with deref A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-discussion Category: Discussion or questions that doesn't represent real issues.
#140340 opened Apr 26, 2025 by Norlock
4
Compile error when directly using &mut in explicity const context A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. 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.
#140126 opened Apr 21, 2025 by RedRam567
5
panic!() with formatting arguments sometimes accepted in const A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-panic Area: Panicking machinery C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-const-eval Working group: Const evaluation
#139621 opened Apr 10, 2025 by m-ou-se
1
12
Compiler panicked at 'is_signed on non-scalar ABI' during const evaluation on windows-sys crate A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) 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.
#138971 opened Mar 26, 2025 by AqourSoro
3
ICE: expected SIMD field to have definite array size A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-SIMD Area: SIMD (Single Instruction Multiple Data) 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. WG-const-eval Working group: Const evaluation
#137291 opened Feb 19, 2025 by folkertdev
3
ICE: "Missing value for constant, but no error reported?" with unresolvabe const due to trivial bounds A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. F-trivial_bounds `#![feature(trivial_bounds)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ 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.
#135617 opened Jan 17, 2025 by FedericoBruzzone
1
@BoxyUwU
4
[ICE]: Both stable and nightly crash at compiler/rustc_const_eval/src/interpret/operand.rs:84:42 on the invalid code under opt-level=3 A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#135128 opened Jan 5, 2025 by wangbo15
2 of 4 tasks
13
ICE: expected wide pointer extra data (e.g. slice length or trait object vtable) A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133966 opened Dec 6, 2024 by matthiaskrgr
4
temporary value dropped while borrowed A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. 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. WG-const-eval Working group: Const evaluation
#132578 opened Nov 3, 2024 by vickenty
2
Recursive const stability checks do not apply in const items A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-stability Area: `#[stable]`, `#[unstable]` etc. C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. WG-const-eval Working group: Const evaluation
#132536 opened Nov 2, 2024 by RalfJung
2
Rust compiler hangs when pretty-printing MIR for a constant A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-MIR Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.html C-bug Category: This is a bug. I-hang Issue: The compiler never terminates, due to infinite loops, deadlock, livelock, etc. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132122 opened Oct 25, 2024 by celinval
3
ICE: no non-'#[track_caller]' frame found A-attributes Area: Attributes (`#[…]`, `#![…]`) A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ 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.
#131787 opened Oct 16, 2024 by matthiaskrgr
@jdonszelmann
4
rustdoc panics while documenting panicking associated constant A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#131625 opened Oct 12, 2024 by joshlf
@fmease
1
const_heap feature can be used to leak mutable memory into final value of constant A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. F-const_heap `#[feature(const_heap)]` F-const_mut_refs `#![feature(const_mut_refs)]` F-core_intrinsics Issue in the "core intrinsics" for internal usage only. P-low Low priority requires-incomplete-features This issue requires the use of incomplete features.
#129233 opened Aug 18, 2024 by RalfJung
rustdoc prints the names of private consts when used as const generic parameter defaults A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-const-generics Area: const generics (parameters and arguments) A-visibility Area: Visibility / privacy C-bug Category: This is a bug. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
#129035 opened Aug 13, 2024 by kpreid
Support for pointers with asm_const A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-rust-for-linux Relevant for the Rust-for-Linux project C-feature-request Category: A feature request, i.e: not implemented / a PR. E-medium Call for participation: Medium difficulty. Experience needed to fix: Intermediate. F-asm `#![feature(asm)]` (not `llvm_asm`) I-lang-nominated Nominated for discussion during a lang team meeting. P-low Low priority T-lang Relevant to the language team, which will review and decide on the PR/issue.
#128464 opened Jul 31, 2024 by Darksonn
@nbdd0121
24
Encountering the type length limit ICEs Miri A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) 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.
#127699 opened Jul 13, 2024 by saethlin
6
ICE: invalid asymmetric binary op A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. F-generic_const_exprs `#![feature(generic_const_exprs)]` I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ requires-incomplete-features This issue requires the use of incomplete features. S-bug-has-test Status: This bug is tracked inside the repo by a `known-bug` test. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125768 opened May 30, 2024 by matthiaskrgr
3
Confusing diagnostic when doing a recursive call in a const block in a const fn: "cycle detected when elaborating drops" A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-diagnostics Area: Messages for errors, warnings, and lints D-confusing Diagnostics: Confusing error or lint that should be reworked. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125713 opened May 29, 2024 by theemathas
Calling non-const function core::slice::iter::<impl IntoIterator for &[u8]>::into_iter A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-diagnostics Area: Messages for errors, warnings, and lints D-terse Diagnostics: An error or lint that doesn't give enough information about the problem at hand. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125490 opened May 24, 2024 by jaudiger
3
The const-eval interpreter is called on incomplete/invalid/ill-formed code A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124789 opened May 6, 2024 by RalfJung
@oli-obk
4
Constant evaluation cannot have code coverage instrumentation A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) 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.
#124732 opened May 5, 2024 by clarfonthey
9
Tracking Issue for const_eval_select A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team, which will review and decide on the PR/issue.
#124625 opened May 2, 2024 by RalfJung
5 tasks
7
Types and specifically "mentioned items" take up a lot of space in Rust metadata files A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-metadata Area: Crate metadata C-optimization Category: An issue highlighting optimization opportunities or PRs implementing such 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.
#122936 opened Mar 23, 2024 by RalfJung
6
Evaluating constants in MIR optimizations introduces const eval errors A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-mir-opt Area: MIR optimizations A-monomorphization Area: Monomorphization C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#122828 opened Mar 21, 2024 by tmiasko
11
ProTip! no:milestone will show everything without a milestone.