id
stringlengths 8
11
| text
stringlengths 32
472
| label
stringclasses 5
values | label_id
int64 0
4
|
|---|---|---|---|
rust_150179
|
Tracking issue for release notes of #150151: Destabilise `target-spec-json` | This issue tracks the release notes text for #150151. cc @davidtwco, @Kivooeo -- original issue/PR authors and assignees for drafting text See the forge.rust-lang.org chapter about [release notes](https://forge.rust-lang.org/release/release-notes.html#preparin | labels: T-compiler, relnotes, relnotes-tracking-issue
|
medium
| 2
|
rust_152771
|
[ICE]: assertion failed: !deep_decl.is_glob_import() while building with 2026-02-11 nightly compiler | ### Meta I am using a nightly version of the compiler. `rustc --version --verbose`: ``` rustc 1.93.1 (01f6ddf75 2026-02-11) binary: rustc commit-hash: 01f6ddf7588f42ae2d7eb0a2f21d44e8e96674cf commit-date: 2026-02-11 host: x86_64-pc-windows-msvc release: 1.93.1 | labels: I-ICE, T-compiler, C-bug
|
question
| 4
|
rust_151729
|
rustc is not building for custom targets | rustc is not building for custom targets with the current nightly branch. I suspect this is related to the following [commit](https://github.com/rust-lang/rust/pull/150151) As mentioned in the commit, I tried passing the `-Zunstable-options` flag using the fol | labels: T-compiler, C-discussion, A-targets
|
question
| 4
|
rust_152585
|
linking with cc failed, could not compile rustc-main due to undef reference | <!-- Thank you for submitting a bootstrap report! Please provide detailed information to help us reproduce and diagnose the issue. --> ### Summary <!-- Provide a brief description of the problem you are experiencing. --> ### Command used ```sh ./x.py build --s | labels: T-bootstrap, C-bug
|
medium
| 2
|
rust_97270
|
box syntax creates Box<T> where T is not yet initialized | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> I tried this code: ```rust #![feature(box_syntax)] fn main() { let _x = box return; } ``` miri reports | labels: A-MIR, C-bug, A-miri, A-box
|
medium
| 2
|
rust_152501
|
`try bikeshed $ty { … }` is not pre-expansion gated (affects beta+nightly) | The following code compiles even though it shouldn't: ```rs fn main() { #[cfg(false)] try bikeshed () {} } ``` Contrary to `try { … }` it does not even issue a pre-expansion gate *warning*. For context, try blocks and some other ancient features are notoriousl | labels: A-parser, P-high, T-compiler, regression-from-stable-to-beta, C-bug
|
critical_bug
| 0
|
rust_152601
|
[ICE]: cargo doc panicked | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: T-rustdoc, I-ICE, C-bug, A-rustdoc-scrape-examples, S-has-mcve, D-Unicode-unaware
|
high
| 1
|
rust_152692
|
Trait-not-implemented diagnostics consider all compiler-internal traits to be unstable | https://github.com/rust-lang/rust/pull/151036 improved trait-not-implemented diagnostics in some cases, by explicitly mentioning that the trait in question is unstable: https://github.com/rust-lang/rust/blob/139651428df86cf88443295542c12ea617cbb587/compiler/ru | labels: A-diagnostics, T-compiler, C-bug, A-contributor-roadblock
|
question
| 4
|
rust_152518
|
[ICE]: fulfillment_errors: index out of bounds: the len is 1 but the index is 1 | <!-- [31mICE[0m: Rustc ./a.rs '-Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_trait_selection/src/error_reporting/traits/fulfillment_errors.rs:285:94: 'index out of bounds: the len is 1 but the index | labels: I-ICE, T-compiler, C-bug, WG-trait-system-refactor
|
high
| 1
|
rust_131891
|
projecting to assoc type of supertrait that is implemented differently for trait object goes wrong | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> I tried this code: [playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gi | labels: A-associated-items, I-unsound, C-bug, T-types, A-dyn-trait, F-ptr_metadata
|
medium
| 2
|
rust_148203
|
ICE with dyn of subtrait of Pointee | ### Code ```Rust #![feature(ptr_metadata)] use std::ptr::Pointee; pub trait SubPointee: Pointee<Metadata = Self::SubMetadata> { type SubMetadata; } impl<T: ?Sized> SubPointee for T { type SubMetadata = <T as Pointee>::Metadata; } pub fn foo<T: SubPointee + ?Si | labels: I-ICE, A-trait-system, T-compiler, C-bug, T-types, A-dyn-trait
|
high
| 1
|
rust_128933
|
Allow exactly one mutable reference even after multiple immutable reference in same scope | I think there is no issue with allowing one mutable reference with any number of immutable references in single scope.Having single mutable reference ensure there is one and only one mutator, while all immutable reference can yet access the mutated information | labels: A-borrow-checker, C-discussion
|
question
| 4
|
rust_152719
|
[ICE]: assertion failed: !deep_decl.is_glob_import() | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: I-ICE, T-compiler, C-bug
|
high
| 1
|
rust_152079
|
`unused_assignments` false positive on diverging path | ### Code ```Rust #[deny(unused_assignments)] fn main() { let mut x = 1; catch(|| { x = 2; // <- panic!(); }); dbg!(x); } fn catch<F: FnOnce()>(f: F) { if let Ok(true) = std::fs::exists("may_or_may_not_call_f") { _ = std::panic::catch_unwind(std::panic::AssertU | labels: A-diagnostics, P-high, T-compiler, regression-from-stable-to-stable, L-unused_assignments
|
critical_bug
| 0
|
rust_141726
|
Unify and deduplicate float tests | We currently have at least two somewhat independent places where float functions are being tested: - in `coretests/tests/float/mod.rs` - in `coretests/tests/floats/f*.rs` - in `std/tests/floats/f*.rs` - In `tests/ui/float/conv-bits-runtime-const.rs` Confusingl | labels: E-easy, C-cleanup, A-testsuite, E-mentor, T-libs, A-floating-point
|
low
| 3
|
rust_133469
|
test issue | nothing to see <!-- TRIAGEBOT_START --> <!-- TRIAGEBOT_SUMMARY_START --> ### Summary Notes - [Note](https://github.com/rust-lang/rust/issues/133469#issuecomment-2865978181) by [Urgau](https://github.com/Urgau) - [This is a test](https://github.com/rust-lang/ru
|
medium
| 2
|
rust_148730
|
ICE `type_of` called on const argument's anon const before the const argument was lowered | <!-- [31mICE[0m: Rustc ./E9C667014C7F35C10F67DFA23F3B84C38C0774A3749594110DD5CF51B15DDA3A.rs '-Zcrate-attr=feature(min_generic_const_args) -ooutputfile -Zdump-mir-dir=dir' 'error: internal compiler error: `type_of` called on const argument's anon const befor | labels: I-ICE, T-compiler, C-bug, F-min_generic_const_args
|
high
| 1
|
rust_53667
|
Tracking issue for eRFC 2497, "if- and while-let-chains, take 2" | # Note: This feature was stabilized in 1.88.0 but on edition 2024 only. If you are using 1.88.0+ and get an error that the feature is still unstable, please upgrade the edition. This is a tracking issue for the eRFC *"if- and while-let-chains, take 2"* (rust-l | labels: B-RFC-approved, T-lang, C-tracking-issue, F-let_chains, S-tracking-ready-to-stabilize
|
question
| 4
|
rust_104893
|
let chains testing | The appearance of #104843 has shown that bugs might still be in hiding for let chains. In order to make the implementation of let chains in rustc more robust, it would be useful to increase the number of places let chains are tested in. There is an automatted | labels: F-let_chains
|
medium
| 2
|
rust_151647
|
ICE: mGCA+GCI: Broken MIR: equate_normalized_input_or_output: NoSolution | Found while investigating an unrelated mGCA issue. --- ```rs #![feature(generic_const_items, min_generic_const_args)] #[type_const] const CT<T: ?Sized>: usize = { <T as Trait>::N }; trait Trait { #[type_const] const N: usize; } impl<T: ?Sized> Trait for T { #[ | labels: I-ICE, T-compiler, C-bug, S-has-mcve, F-generic_const_items, F-min_generic_const_args
|
high
| 1
|
rust_135974
|
Tracking Issue for `Vec::push_mut` | Feature gate: `#![feature(push_mut)]` This is a tracking issue for `Vec::push_mut` and similar methods, as discussed in the comments of [this ACP](https://github.com/rust-lang/libs-team/issues/465). This adds a way to get a reference to the just-pushed value, | labels: T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period, I-lang-radar
|
question
| 4
|
rust_152588
|
[ICE]: assertion failed: !deep_decl.is_glob_import() | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: A-resolve, I-ICE, T-compiler, C-bug
|
high
| 1
|
rust_115336
|
`extern "C" fn` on sparc64 targets does not respect repr(transparent) | I tried the following code: ```rust #![feature(rustc_attrs)] #[rustc_abi(debug)] extern "C" fn test1(_x: [u8; 0]) {} #[repr(transparent)] struct Wrap<T>(T); #[rustc_abi(debug)] extern "C" fn test2(_x: Wrap<[u8; 0]>) {} ``` When running this with `--target spar | labels: A-FFI, P-high, T-compiler, I-unsound, O-SPARC, A-ABI
|
high
| 1
|
rust_150018
|
assertion failed: trying to encode a dep node twice | As I've suspected #149916 revealed a bug in rustc's query system on multiple threads. I was trying to build rustc itself with the nightly toolchain as stage0 after doing `git checkout` build fails while trying to compile `rustc_lint_defs`. ### Error ``` thread | labels: I-ICE, T-compiler, A-incr-comp, C-bug, A-parallel-compiler
|
high
| 1
|
rust_141738
|
ICE:unexpected `DefKind` for const alias to resolve to: Ctor(Struct, Const) | The code is generated by a fuzzer and reduced manually _It may be a duplicate of #139596 , but I'm not quite sure, so I'm raising this issue._ _Thank you very much for your correction._ <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try | labels: I-ICE, E-needs-test, T-compiler, C-bug, F-min_generic_const_args
|
high
| 1
|
rust_152493
|
Error on incomplete macro call could provide more context, specially for built-in macros like `write!` not receiving the `Formatter` | ### Code ```Rust struct S; impl std::fmt::Display for S { fn fmt (&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result { match self { S => write!("S"), } } } ``` ### Current output ```Shell error: unexpected end of macro invocation --> src/lib.rs:5:28 | | labels: A-diagnostics, P-low, A-macros, T-compiler
|
low
| 3
|
rust_152263
|
[ICE]: Corrupted .rmeta data causes panic | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: I-ICE, T-compiler, C-bug
|
high
| 1
|
rust_76001
|
Tracking Issue for inline const patterns (RFC 2920) | This is a tracking issue for the RFC "Inline `const` expressions and patterns" (rust-lang/rfcs#2920). Const expressions have been stabilized, but patterns have not The feature gate for the issue is `#![feature(inline_const_pat)]`. This was originally a trackin | labels: B-RFC-approved, T-lang, T-compiler, C-tracking-issue, A-const-eval, F-inline_const
|
question
| 4
|
rust_59490
|
eventual goal: re-remove leak-check from compiler | PR #58592 re-added the so-called leak check. Re-adding the leak-check masked a number of bugs, where you need to use `-Z no-leak-check` to observe them again. We plan to eventually re-remove the leak check. But before doing so, we need to double-check that all | labels: T-compiler, C-tracking-issue, S-tracking-unimplemented, T-types
|
medium
| 2
|
rust_60471
|
Tracking issue for "Lazy normalization" | # What is this? "Lazy normalization" is a change to how we handle associated types (and constants) so that we wait until we have to equate an associated type (or constant) has to be equated or processed to normalize it (i.e., figure out if there is an impl we | labels: A-type-system, A-trait-system, T-compiler, C-tracking-issue, A-const-generics, A-lazy-normalization
|
medium
| 2
|
rust_152030
|
ICE when coercing a too large array to a trait object | ### Code ```Rust #![feature(try_as_dyn)] trait Trait {} impl Trait for [u8; 1<<63] {} pub fn foo(x: &[u8; 1<<63]) { let _ = std::any::try_as_dyn::<[u8; 1<<63], dyn Trait>(x); } ``` Tracking issue for `try_as_dyn`: #144361 ### Meta Reproducible on the playgroun | labels: I-ICE, P-medium, T-compiler, regression-from-stable-to-stable, C-bug, A-layout
|
critical_bug
| 0
|
rust_142152
|
ICE compiler/rustc_query_system/src/dep_graph/query.rs index out of bounds | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: I-ICE, T-compiler, A-incr-comp, C-bug, A-parallel-compiler, S-has-mcve
|
high
| 1
|
rust_133966
|
ICE: `expected wide pointer extra data (e.g. slice length or trait object vtable)` | <!-- [31mICE[0m: Rustc ./a.rs '' 'error: internal compiler error: compiler/rustc_const_eval/src/interpret/place.rs:36:17: expected wide pointer extra data (e.g. slice length or trait object vtable)', 'error: internal compiler error: compiler/rustc_const_eval | labels: I-ICE, T-compiler, C-bug, A-const-eval, S-has-mcve, S-bug-has-test
|
high
| 1
|
rust_150983
|
ICE: `ty::ConstKind::Error constructed but no error reported` | <!-- [31mICE[0m: Rustc ./a.rs '-Zincremental-verify-ich=yes -Cincremental=<dir> -Cdebuginfo=2 -Clink-dead-code=true -Zvalidate-mir -Zquery-dep-graph -Zthreads=4 --edition=2024' 'error: internal compiler error: ty::ConstKind::Error constructed but no error re | labels: I-ICE, T-compiler, C-bug, F-generic_const_parameter_types, F-generic_const_items, F-unsized_const_params
|
high
| 1
|
rust_151625
|
[ICE]: `ty::ConstKind::Error constructed but no error reported` | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: I-ICE, T-compiler, C-bug, F-adt_const_params, F-unsized_const_params, F-min_generic_const_args
|
question
| 4
|
rust_152354
|
regression: Cargo not rendering json output | The following three crater outputs contain json that rustc output as-is. They are not properly formatted like in other crater outputs. https://crater-reports.s3.amazonaws.com/beta-1.94-2/beta-2026-01-20/reg/atelier_openapi-0.1.0/log.txt https://crater-reports. | labels: regression-from-stable-to-beta, T-cargo, I-prioritize
|
critical_bug
| 0
|
rust_146803
|
Adding generics affect whether code has UB or not, according to Miri | I tried this code: ```rust enum Never {} #[repr(u64, C)] #[allow(dead_code)] enum Thing<T> { Never(T) = 0, Inhabited = 1, } fn main() { assert_eq!(size_of::<Thing<Never>>(), 8); let data = 0u64; // Discriminant is 0, so we should have Thing::Never let thing_re | labels: T-compiler, A-MIR, C-bug, A-miri, A-patterns, A-exhaustiveness-checking
|
medium
| 2
|
rust_142394
|
`match` on uninhabited type does not trigger UB in Miri | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> I tried this code: ```rust #![allow(deref_nullptr)] enum Never {} fn main() { unsafe { match *std::ptr | labels: T-compiler, A-MIR, C-bug, A-miri, A-patterns, A-exhaustiveness-checking
|
medium
| 2
|
rust_146590
|
Uninhabited types have strange borrow-checking behavior, even behind references | I'm not sure if this is a bug or not. ```rust enum Never {} fn works(x: &mut Result<Never, String>) { match x { &mut Ok(ref mut y) => match x { &mut Err(ref mut z) => { let _y = y; let _z = z; } _ => {} }, _ => {} }; } fn fails(x: &mut Result<String, String>) | labels: A-borrow-checker, T-lang, T-compiler, C-bug, A-patterns, A-exhaustiveness-checking
|
medium
| 2
|
rust_152545
|
[ICE]: `invalid rigid alias in layout_of after normalization` | <!-- [31mICE[0m: Rustc ./a.rs '' 'thread 'rustc' ($TID) panicked at compiler/rustc_ty_utils/src/layout.rs:780:17: 'internal error: entered unreachable code: invalid rigid alias in layout_of after normalization: Alias(Projection, AliasTy { args: [Alias(Projec | labels: I-ICE, P-high, T-compiler, regression-from-stable-to-beta, C-bug
|
critical_bug
| 0
|
rust_73321
|
Search in associated items when type cannot be found | [Given the following code](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=e0d291d80bd21afde1f4661358ec95f8): https://github.com/rust-lang/rust/blob/1fb612bd15bb3ef098fd24c20d0727de573b4410/src/test/ui/associated-types/associated-types | labels: C-enhancement, A-diagnostics, T-compiler, A-suggestion-diagnostics, D-papercut, D-terse
|
low
| 3
|
rust_152014
|
We generally emit an additional error if a trait object lifetime bound defaults to an unresolved lifetime in item signatures | If we fail to deduce a trait object lifetime default in an item signature[^1] we generally emit an error for that. More specifically, we generally do that if `TyCtxt::named_bound_var` returns `None`. For context, `named_bound_var` actually returns `None` iff R | labels: A-diagnostics, A-lifetimes, T-compiler, D-verbose, S-has-mcve, A-dyn-trait
|
medium
| 2
|
rust_148854
|
Lifetime bounds of Drop aren't checked properly | This unsoundness is an exploitation of the weirdness in https://github.com/rust-lang/rust/issues/115175. The below code causes use-after-free in safe code. (Prints garbage data in my testing.) In the function `extend`, rust should have prohibited constructing | labels: A-lifetimes, A-destructors, A-borrow-checker, P-high, T-compiler, I-unsound
|
critical_bug
| 0
|
rust_115175
|
ignored lifetime constraints in type annotations | The following compiles since the full transition to NLL in v1.63, although it shouldn't: ```rust struct Static<T: 'static>(T); fn test<T>() { let _ = None::<Static<T>>; } ``` | labels: P-medium, T-compiler, regression-from-stable-to-stable, I-unsound, A-NLL, C-bug
|
critical_bug
| 0
|
rust_152539
|
`riscv64a23-unknown-linux-gnu` promotion not reflected in docs | ### Location (URL) https://doc.rust-lang.org/rustc/platform-support.html ### Summary According to rust 1.93.0 release notes `riscv64a23-unknown-linux-gnu` platform got promoted to Tier 2 (without host tools) in: #148435. However platform support page, linked i | labels: E-easy, A-docs, O-riscv, A-targets
|
question
| 4
|
rust_151330
|
[ICE]: vtable : `None` from `prepare_vtable_segments()` | <!-- [31mICE[0m: Rustc ./4D3F8D4D46E1245F68AAAD1F329B376BA3166264E585638CB073374363186000.rs '-Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_trait_selection/src/traits/vtable.rs:437:77: 'called `Opti | labels: I-ICE, T-compiler, C-bug, WG-trait-system-refactor
|
high
| 1
|
rust_151414
|
Regression after #150603: misleading error for complex const generic arguments | ### Code ```Rust #![feature(adt_const_params, min_generic_const_args)] const fn bar() -> [u64; 1] { [42] } struct Foo<const P: [u64; 1]>(()); fn main() { let _ = Foo::<{ bar() }>; } ``` ### Current output ```Shell error: tuple constructor with invalid base pat | labels: A-diagnostics, T-compiler, F-min_generic_const_args
|
high
| 1
|
rust_148953
|
ICE unexpected `DefKind` for const alias to resolve to: `Ctor(Struct, Const)` | <!-- [31mICE[0m: Rustc ./a.rs '' 'thread 'rustc' ($TID) panicked at compiler/rustc_middle/src/ty/instance.rs:516:9: 'assertion `left matches right` failed: `Instance::try_resolve` should only be used to resolve instances of functions, statics, and consts; to | labels: I-ICE, T-compiler, C-bug, F-min_generic_const_args
|
high
| 1
|
rust_135845
|
ICE: `cannot convert ReLateParam to a region vid` | <!-- [31mICE[0m: Rustc ./a.rs '' 'error: internal compiler error: compiler/rustc_borrowck/src/universal_regions.rs:888:36: cannot convert `ReLateParam(DefId(0:16 ~ a[ff78]::get_invariant_ref), BrNamed(DefId(0:17 ~ a[ff78]::get_invariant_ref::'a), 'a))` to a | labels: I-ICE, T-compiler, C-bug, S-bug-has-test
|
high
| 1
|
rust_152499
|
Inline const patterns are no longer pre-expansion gated | Found while running [fmease/rasur](https://github.com/fmease/rasur) against the UI test suite (that's part of why I've written this parser in the first place, nice!). --- Example reproducers: These two programs now get accepted on beta and nightly even though | labels: A-parser, T-compiler, regression-from-stable-to-beta, C-bug, P-critical, A-patterns
|
critical_bug
| 0
|
rust_152231
|
FileTimes::set_modified does not modify the time, but returns FileTimes | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> I tried this code: https://doc.rust-lang.org/std/fs/struct.FileTimes.html#method.set_modified ```rust | labels: E-easy, C-enhancement, A-filesystem, D-lack-of-suggestion
|
low
| 3
|
rust_152470
|
[autodiff] compiler error when differentiating functions (like powi) | Follow up of [#wg-autodiff > Simplify autodiff handling of dependencies (rlib) @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/390790-wg-autodiff/topic/Simplify.20autodiff.20handling.20of.20dependencies.20.28rlib.29/near/573014613) for @ZuseZ4 and @sgasho | labels: T-compiler, C-bug, F-autodiff
|
low
| 3
|
rust_150899
|
Better help text for incorrect `macro_rules!` usage | ### Code ```Rust macro_rules!(i_think_the_name_should_go_here) { () => {} } ``` ### Current output ```Shell error: macros that expand to items must be delimited with braces or followed by a semicolon --> src/lib.rs:1:13 | 1 | macro_rules!(i_think_the_name_shou | labels: A-diagnostics, A-macros, T-compiler
|
medium
| 2
|
rust_104463
|
Misleading comments over methods on `TyCtxtEnsure` in `rustc_middle::mir::interpret::queries` | > These comments (also the one below) are wrong now -- they talk about the return value of a function that doesn't return anything! I have no idea what is going on here so if someone could make a PR to update the comments, that would be much appreciated. :) _O | labels: A-docs, C-bug, A-contributor-roadblock, A-query-system
|
question
| 4
|
rust_152510
|
Cleanup: go through `bootstrap.py` and make sure we specify explicit `open()` encodings | > Remark: we should go through `bootstrap.py` and make sure we specific explicit `open()` encodings, as far as I am aware there is a reasonable desire to want to make a future change in Python 3.* where `open()` defaults to UTF-8 encoding, which could break `o | labels: C-cleanup, T-bootstrap, A-Python
|
question
| 4
|
rust_147465
|
Rust 1.90 causes Wasm crash by out of memory | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> After updating to Rust 1.90.0, Wasm becomes to be crashed by out of memory. The reproduce senquence is | labels: I-crash, regression-from-stable-to-nightly, O-wasm, C-bug, C-external-bug
|
critical_bug
| 0
|
rust_145866
|
RISC-V Extension Changes coming to LLVM 22 | In LLVM 22.x, we intend to simplify how the C and Zc* extensions are handled in the LLVM backend, in the change llvm/llvm-project#155035. This should more closely align with how these instructions are specified in the RISC-V specification. In clang, we are rel | labels: A-LLVM, T-compiler, O-riscv
|
medium
| 2
|
rust_128203
|
Tracking Issue for `rwlock_downgrade` | <!-- Thank you for creating a tracking issue! Tracking issues are for tracking a feature from implementation to stabilization. Make sure to include the relevant RFC for the feature if it has one. If the new feature is small, it may be fine to skip the RFC proc | labels: T-libs-api, C-tracking-issue
|
question
| 4
|
rust_147370
|
Tracking issue for enabling main rust-analyzer tests in r-l/r CI | ## Summary Currently, we only run a tiny subset of r-a tests (namely `proc-macro-srv`). We would like to make sure r-a is well-tested against Tier 1 platforms, and catch more r-a (and even rustc-induced) regressions, by running the main r-a tests as well. ## S | labels: T-bootstrap, T-infra, C-tracking-issue, A-CI, A-test-infra, T-rust-analyzer
|
question
| 4
|
rust_148372
|
Tracking issue for MCP 923: Run main rust-analyzer tests in rust-lang/rust CI | This is a tracking issue for MCP "Run main rust-analyzer tests in rust-lang/rust CI" (rust-lang/compiler-team#923). > [!NOTE] > Tracking issues are used to record the overall progress of implementation. > They are also used as hubs connecting to other relevant | labels: T-compiler, C-tracking-issue, B-MCP-approved
|
question
| 4
|
rust_151807
|
rustc miscompiled on powerpc64 after LLVM 22 update | ### Code I don't have the ability to reproduce but this comes from a `cargo install cargo-nextest` on PPC64le, building gimli. Happened with this CI run: https://github.com/rust-lang/compiler-builtins/actions/runs/21465837588/job/61827742076?pr=1064 ### Meta V | labels: A-LLVM, I-ICE, regression-from-stable-to-nightly, P-high, T-compiler, O-PowerPC
|
critical_bug
| 0
|
rust_148738
|
Tracking Issue for minimal const `ControlFlow` methods (`min_const_control_flow`) | <!-- Thank you for creating a tracking issue! Tracking issues are for tracking a feature from implementation to stabilization. Make sure to include the relevant RFC for the feature if it has one. If the new feature is small, it may be fine to skip the RFC proc | labels: T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period, S-tracking-ready-to-stabilize
|
question
| 4
|
rust_71043
|
Lint exported_private_dependencies misses public dependency via trait impl | Tracking issue: #44663, RFC: rust-lang/rfcs#1977 Cargo.toml: ```toml cargo-features = ["public-dependency"] [package] name = "playground" version = "0.0.0" edition = "2018" [dependencies] num-traits = "0.2" ``` lib.rs: ```rust pub struct S; impl std::ops::Add | labels: A-lints, A-visibility, T-compiler, C-bug, L-exported_private_dependencies, F-public_private_dependencies
|
medium
| 2
|
rust_143531
|
`private_interfaces` not linting RPITIT | ### Code ```Rust trait Bar {} pub trait Foo { fn foo() -> impl Bar; } fn main() {} ``` ### Current output Empty output with no warnings. ### Desired output ```Shell warning: trait `Bar` is more private than the item `Foo::foo` --> foo.rs:4:1 | 4 | fn foo() -> | labels: A-lints, A-visibility, T-compiler, A-impl-trait, C-bug, L-private_interfaces
|
medium
| 2
|
rust_151832
|
SIGSEGV during stage1 compilation of `proc_macro` for `i686-win7-windows-msvc` | Cross-compiling the stage1 from `x86_64-unknown-linux-gnu` to `i686-win7-windows-msvc` now seems to crash during the compilation of `proc_macro`: ``` Building stage1 library artifacts (stage1:x86_64-unknown-linux-gnu -> stage1:i686-win7-windows-msvc) Compiling | labels: I-crash, A-LLVM, T-compiler, C-bug, A-proc-macros, llvm-fixed-upstream
|
high
| 1
|
rust_71850
|
Reuse LTO products for incremental builds when deps are unchanged | Incremental builds with LTO (`thin` or `fat`) always take the same amount of time (~10s on [my project](https://github.com/fenollp/reMarkable-tools/tree/730e3fc2c100a713abdeebeb434a9d86aa2a48cc/marauder)) when dependencies are unchanged. It seems to take as lo | labels: A-linkage, C-enhancement, I-compiletime, T-compiler
|
low
| 3
|
rust_49569
|
Cryptic LTO-related error message when performing `include_bytes!` on large files | When trying to include a large (> 500MiB) binary in a program, the compiler crashes with an error message relating to LTO (Link time optimization?) I tried this code: ```rust fn main() { // the file below was generated with // $ dd if=/dev/urandom of=output.da | labels: A-codegen, A-diagnostics, T-compiler, C-bug
|
medium
| 2
|
rust_152347
|
regression: name resolution fails to find constant? | I'm not sure if this is our fault or something in the underlying library... ``` [INFO] [stdout] error[E0425]: cannot find value `TEST_MODULE_ID` in this scope [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/abstract-t | labels: A-resolve, T-compiler, regression-from-stable-to-beta, P-critical
|
critical_bug
| 0
|
rust_151124
|
ICE: `DefId(..)): reachable Public > nominal Restricted(DefId(..)` | <!-- [31mICE[0m: Rustc ./a.rs '' 'error: internal compiler error: compiler/rustc_middle/src/middle/privacy.rs:187:21: DefId(0:6 ~ a[1af1]::{use#1}): reachable Public > nominal Restricted(DefId(0:0 ~ a[1af1]))', 'error: internal compiler error: compiler/rustc | labels: I-ICE, A-visibility, T-compiler, C-bug, S-has-mcve, requires-debug-assertions
|
high
| 1
|
rust_152004
|
Regression on nightly: unused pub(crate) use::*; is not actually unused | I encountered this while trying to [bump Rust from `nightly-2026-01-09` to `nightly-2026-02-01`](https://github.com/pola-rs/polars/pull/26379) in Polars. The [CI complains](https://github.com/pola-rs/polars/actions/runs/21599607867/job/62241657031?pr=26379): ` | labels: T-compiler, C-bug, I-prioritize, L-unused_imports
|
high
| 1
|
rust_151791
|
Regression in 1.93.0 `the type <XYZ as Archive>::Archived has an unknown layout` | ### Code I tried the following in a new cargo project. This is minimized from a real codebase. ```toml [package] name = "broken-nightly" version = "0.1.0" edition = "2024" [dependencies] cynic-codegen = { version = "3.12.0", features = [ "rkyv" ] } [profile.de | labels: A-trait-system, A-associated-items, P-high, T-compiler, regression-from-stable-to-stable, C-bug
|
critical_bug
| 0
|
rust_152482
|
Bootstrap Script Error on Windows | I have tried this code on the main branch.: ```rust python x.py build --stage 1 ``` I expected to see this happen: Successful execution. Instead, this happened: Exception occurred. ### Environment ``` Windows 11 Chinese Edition ``` I think this is an encoding | labels: T-bootstrap, C-bug, A-Python
|
medium
| 2
|
rust_74756
|
Uninformative error message when casting usize to pointer to generic `?Sized` type | Trying to compile this code ```rust pub fn bogus_ptr<U: ?Sized>() -> *const U { 0usize as *const U } ``` produces this error message ``` error[E0606]: casting `usize` as `*const U` is invalid --> <source>:2:5 | 2 | 0usize as *const U | ^^^^^^^^^^^^^^^^^^ ``` I | labels: C-enhancement, A-diagnostics, T-compiler, D-papercut, D-terse
|
low
| 3
|
rust_151904
|
Rustdoc syntax highlighting of `ident !=` is displayed as a macro invocation `ident!` | # Code ```rs if layout != Layout::new::<U>() { return Err(new_value); } ``` [Click here to view this live](https://docs.rs/tokio-util/0.7.18/src/tokio_util/sync/reusable_box.rs.html#106) # Expected Outcome The `layout !=` part is displayed in black. # Actual O | labels: T-rustdoc, C-bug, A-rustdoc-ui
|
low
| 3
|
rust_147883
|
"Size::sub: 0 - 8 would result in negative size" ICE on sparc | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: I-ICE, T-compiler, O-SPARC, C-bug, A-ABI
|
high
| 1
|
rust_115399
|
ICE in sparc64 `fn_abi_of_instance` | I tried the following code: ```rust #[repr(transparent)] #[derive(Default)] struct Wrapper2<T>((), T); type T = (i8, i16, f32); extern "C" fn test(x: Wrapper2<T>) {} fn main() { test(Default::default()); } ``` Building this for the sparc64-unknown-linux-gnu ta | labels: I-ICE, T-compiler, O-SPARC, C-bug, A-ABI
|
high
| 1
|
rust_122620
|
sparc64 has incorrect ABI for struct containing f64 and f32 | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> **I tried this code**: ```rust // with --target=sparc64-unknown-linux-gnu #[repr(C)] pub struct Double | labels: P-medium, T-compiler, I-unsound, O-SPARC, C-bug, A-ABI
|
high
| 1
|
rust_141679
|
error message for inherent `impl` on `type` that is external could be more explanatory | ### Code ```Rust use std::rc::Rc; pub struct Foo; pub type Function = Rc<Foo>; impl Function { } ``` ### Current output ```Shell error[E0116]: cannot define inherent `impl` for a type outside of the crate where the type is defined --> src/lib.rs:6:1 | 6 | impl | labels: A-diagnostics, T-compiler, D-terse
|
medium
| 2
|
rust_81059
|
Error message improvement: Manual reborrowing with `&mut *variable` | In this testcase, I wanted to reborrow `outer`, but accidentally wrote `&mut outer` instead of `&mut *outer`. However, the error's suggestion was ```try removing `&mut` here``` which wouldn't have worked. It would be better to have the suggestion ```try adding | labels: A-diagnostics, T-compiler, A-suggestion-diagnostics, D-papercut, D-newcomer-roadblock, D-invalid-suggestion
|
medium
| 2
|
rust_82775
|
Tracking Issue for assert_matches | <!-- Thank you for creating a tracking issue! Tracking issues are for tracking a feature from implementation to stabilization. Make sure to include the relevant RFC for the feature if it has one. If the new feature is small, it may be fine to skip the RFC proc | labels: T-libs-api, C-tracking-issue
|
question
| 4
|
rust_151705
|
Tracking issue for MCP 918: Promote tvOS/watchOS/visionOS to Tier 2 | This is a tracking issue for MCP "Promote tvOS/watchOS/visionOS to Tier 2" (rust-lang/compiler-team#918). > [!NOTE] > Tracking issues are used to record the overall progress of implementation. > They are also used as hubs connecting to other relevant issues, e | labels: T-compiler, C-tracking-issue, S-tracking-unimplemented, O-apple, B-MCP-approved
|
question
| 4
|
rust_151818
|
Unable to build `core` for `powerpc64-ibm-aix` | `cargo +nightly check --target powerpc64-ibm-aix -Zbuild-std=core` (checking the libc crate but that shouldn't matter) is now printing a number of errors like: ```text error: branch target not a multiple of four (242) error: branch target not a multiple of fou | labels: A-LLVM, regression-from-stable-to-nightly, T-compiler, O-PowerPC, WG-llvm, I-prioritize
|
critical_bug
| 0
|
rust_151926
|
LLVM crash in vectorizer when compiling GameCube emulators | code: https://codeberg.org/hazelwiss/solstice/src/commit/34059d531fb8675c6a5b8dc5990ff748c8063ebc ``` error: rustc interrupted by SIGSEGV, printing backtrace /home/nora/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/librustc_driver-1c4195dec9454671.so | labels: I-crash, A-LLVM, regression-from-stable-to-nightly, P-high, C-bug, S-has-mcve
|
critical_bug
| 0
|
rust_152255
|
"Out of memory" error when accessing files from wasm32-wasip2 in rust 1.93.0 | <!-- Title: wasm32-wasip2: fd_close missing from compiled component in 1.93.0, causing file descriptor leak --> Rust 1.93.0 stable produces `wasm32-wasip2` components that are missing the `fd_close` import from `wasi_snapshot_preview1`. File descriptors are ne | labels: regression-from-stable-to-stable, C-bug, P-critical, T-libs, O-wasi, O-wasip2
|
critical_bug
| 0
|
rust_124309
|
std::fs::create_dir_all will stack overflow with big paths | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> I tried this code: ```rust std::fs::create_dir_all(big_path); ``` I expected to see this happen: doesn | labels: C-bug, T-libs, A-io
|
medium
| 2
|
rust_88051
|
Semantically equal `Ordering` matches generate different assembly | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> https://rust.godbolt.org/z/orxr8sffq I tried this code: ```rust use std::cmp::Ordering; pub fn a(x: i3 | labels: I-slow, C-bug
|
medium
| 2
|
rust_152468
|
[ICE]: calling a `Fn` incorrectly in `core` ICEs when making the type error diagnostic | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: I-ICE, T-compiler, C-bug
|
high
| 1
|
rust_152467
|
Types inside higher-ranked binders sometimes aren't checked for WF. | The following code errors ```rust trait Trait: 'static {} fn wut() where for<'a> dyn Trait + 'a + Send:, { } fn main() { wut(); } ``` ``` error: higher-ranked lifetime error --> src/main.rs:10:5 | 10 | wut(); | ^^^^^ | = note: could not prove `for<'a> (dyn Tra | labels: A-type-system, I-ICE, A-trait-system, T-compiler, C-bug, T-types
|
high
| 1
|
rust_151358
|
[ICE]: `!worker_thread.is_null()` | <!-- Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for how to create smaller examples. http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-pat | labels: I-ICE, T-compiler, C-bug, A-parallel-compiler, I-cycle
|
high
| 1
|
rust_152464
|
Incorrect "implementation of `Send` is not general enough" error around AsyncFn | Here is an API that accepts an async function whose future is `Send`, e.g. as a registration mechanism for RPC handlers: ```rust /// Accept an async function that repeatedly processes an incoming reference to /// `i32`, with a future type that can be polled on | labels: C-bug
|
medium
| 2
|
rust_152453
|
rustc 1.93.0 SIGSEGVs or ICEs during `cargo test` | I encountered repeated segmentation faults (SIGSEGV) when attempting to build my Rust project using Rust 1.93.0 with the stable-x86_64-unknown-linux-gnu toolchain. The issue persists even after completely cleaning the project and performing a fresh reinstall o | labels: I-ICE, T-compiler, C-bug
|
high
| 1
|
rust_142778
|
ICE: rustc_query_system: dep_graph: assertion failed (dep node index out of range) | No idea how it came into existence, but people in rust discord said it's better to submit the bug. The code can be found [here](https://github.com/olekspickle/bevy_new_third_person), but I only stumbled on it once so it is not reproducible at least for me. Ver | labels: I-ICE, T-compiler, A-incr-comp, C-bug, requires-nightly, A-parallel-compiler
|
high
| 1
|
rust_141540
|
A dep graph node (mir_drops_elaborated_and_const_checked) does not have an unique index | The error has been occurring sporadically for like a week or two with recent nightly versions. Unfortunately I don't have more details, please let me know if I can help somehow. ### Error output ``` thread 'rustc' panicked at /rustc/3e674b06b5c74adea662bd0b0b0 | labels: I-ICE, T-compiler, A-incr-comp, C-bug, A-parallel-compiler, A-query-system
|
high
| 1
|
rust_111164
|
Out of date information about Rvalue::Aggregate | ### Location rustc_middle::mir::Rvalue::Aggregate ### Summary Following #107267, the statement "Disallowed after deaggregation ..." is not valid anymore. | labels: A-docs, A-contributor-roadblock
|
low
| 3
|
rust_109829
|
implicit Deref coercion not happening | ```rust use std::path::{Path,PathBuf}; #[derive(Clone, Debug, Eq, PartialEq, PartialOrd, Ord)] pub(crate) struct PathBasedToolchain(PathBuf); impl TryFrom<&Path> for PathBasedToolchain { type Error = anyhow::Error; fn try_from(value: &Path) -> std::result::Res | labels: E-easy, A-docs, C-discussion
|
question
| 4
|
rust_143358
|
ICE: `unhandled node ConstArg(ConstArg ` | <!-- [31mICE[0m: Rustc ./a.rs '-Zcrate-attr=feature(generic_const_exprs) -Zcrate-attr=feature(min_generic_const_args) -ooutputfile -Zdump-mir-dir=dir' 'error: internal compiler error: compiler/rustc_hir_analysis/src/collect/generics_of.rs:226:14: unhandled n | labels: I-ICE, E-needs-test, T-compiler, C-bug, F-generic_const_exprs, S-has-mcve
|
high
| 1
|
rust_131292
|
ICE: `bpos.to_u32() >= mbc.pos.to_u32() + mbc.bytes as u32` | <!-- [31mICE[0m: Rustc ./a.rs '' 'thread 'rustc' panicked at compiler/rustc_span/src/lib.rs:2151:17: 'assertion failed: bpos.to_u32() >= mbc.pos.to_u32() + mbc.bytes as u32'', 'thread 'rustc' panicked at compiler/rustc_span/src/lib.rs:2151:17: 'assertion fai | labels: I-ICE, T-compiler, C-bug, S-bug-has-test
|
high
| 1
|
rust_152376
|
`IntoFuture` allows contradictory associated type equality bounds | <!-- Thank you for filing a bug report! 🐛 Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. --> I tried this code: ```rust use std::future::{IntoFuture, Ready}; async fn test<T>(t: T) -> u32 where T | labels: C-discussion, A-impossible-bounds
|
question
| 4
|
rust_151273
|
ICE: `thir_body queried for type_const` (via cfg_attr) | I found this with the following code: ```rust #![allow(incomplete_features)] #![feature(min_generic_const_args)] pub trait Foo { #[cfg_attr(feature = "some_feature", type_const)] const N: usize; } impl Foo for u32 { #[cfg_attr(feature = "some_feature", type_co | labels: I-ICE, T-compiler, C-bug, requires-debug-assertions, F-min_generic_const_args
|
high
| 1
|
rust_80317
|
Function pointer does not fulfill the required lifetime | Function pointers have no lifetime of their own, and essentially are `'static` ([Unsafe Code Guidelines Reference](https://rust-lang.github.io/unsafe-code-guidelines/layout/function-pointers.html)), so I would expect `fn(T) -> U: 'a` to hold for any lifetime ` | labels: A-lifetimes, C-bug, T-types
|
medium
| 2
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 6