Upload 4 files

test_labeled.jsonl

@@ -0,0 +1,100 @@
+{"id": "rust_138274", "text": "[bug] When I Use tauri-plugin-http and reqwest either, I got a 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, P-medium, T-compiler, regression-from-stable-to-stable, C-bug, A-coercions", "label": "critical_bug", "label_id": 0}
+{"id": "rust_137916", "text": "ICE Unsize coercion, but `Box<{async block@file.rs}>` isn't coercible to `Box<dyn Send>` | <!-- 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, E-mentor, T-compiler, E-medium, C-bug, S-has-mcve", "label": "high", "label_id": 1}
+{"id": "rust_151323", "text": "[ICE]: !tcx.next_trait_solver_globally() | <!-- \u001b[31mICE\u001b[0m: Rustc ./2969A4590773DF5416935FBB7FE10D4070C5F412CB47CD0E21F34E735F4A479B.rs '--edition=2024 -Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_hir_analysis/src/collect/type_of/opaque.rs: | labels: I-ICE, T-compiler, C-bug, WG-trait-system-refactor", "label": "high", "label_id": 1}
+{"id": "rust_142931", "text": "normalize_lexically should mention other functions that do basic normalization | ### Location https://doc.rust-lang.org/nightly/std/path/struct.Path.html#method.normalize_lexically ### Summary both the PartialEq impl for Path and Path::components will normalize away non-leading `.` and duplicate/trailing slashes. This is \"good enough\" for  | labels: A-docs, T-libs", "label": "low", "label_id": 3}
+{"id": "rust_151322", "text": "[ICE]: !self.tcx.next_trait_solver_globally() | <!-- 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-type_alias_impl_trait, WG-trait-system-refactor", "label": "high", "label_id": 1}
+{"id": "rust_145989", "text": "std::pointer::Nonnull should guarantee ABI compatibility for non-null pointer values | Can we rely on `NonNull<T>` having the same representation as `*mut T` for all non-null values of that type? In particular, can we rely on e.g. `NonNull<std::ffi::c_void>` being ABI compatible with C `void*` for non-null pointers? It seems pretty likely that t | labels: T-libs-api, A-raw-pointers, C-discussion, T-opsem", "label": "question", "label_id": 4}
+{"id": "rust_144060", "text": "Lint regression: `dead_code` ignores `#[allow(dead_code)]` on traits | ### Code ```rust #[allow(dead_code)] trait Foo { const FOO: u32; } impl Foo for u32 { const FOO: u32 = roundtrip(0); } const fn roundtrip(x: u32) -> u32 { x } ``` https://play.rust-lang.org/?version=nightly&mode=debug&edition=2024&gist=1991c4121122ea00f92d7386 | labels: A-diagnostics, P-low, T-compiler, regression-from-stable-to-stable, L-false-positive, I-lang-radar", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151026", "text": "stable compiler should provide better advice for `Step` trait failures | ### Code ```Rust fn custom_range() { struct Foo(u32); let x = Foo(0); let y = Foo(10); for value in x..y {} } ``` ### Current output ```Shell error[E0277]: the trait bound `Foo: Step` is not satisfied --> src/lib.rs:7:18 | 7 | for value in x..y {} | ^^^^ unsat | labels: A-diagnostics, T-compiler", "label": "question", "label_id": 4}
+{"id": "rust_82171", "text": "Unclear compiler error when `impl Trait` return value captures non-'static argument | (cc @estebank) I tried this code (the explicit `'static` lifetime is unnecessary but emphasizes the implicit `'static` requirement of `impl Trait`): ```rust fn foo<T>(a: T) -> impl Iterator<Item = String> + 'static where T: std::fmt::Display { std::iter::once( | labels: A-diagnostics, A-lifetimes, T-compiler, A-impl-trait, C-bug, D-papercut", "label": "medium", "label_id": 2}
+{"id": "rust_152262", "text": "`-Clinker-plugin-lto` is required for inlining stdlib with LTO | ## Experiment setup Considering the following code: ```rust #![no_main] extern \"C\" { fn ftn() -> u32; } #[unsafe(export_name = \"_start\")] fn _start() -> f64 { let f77 = unsafe { ftn() } as f64; f64::cbrt(f77) } ``` The code is incorrect but quite good for demo | labels: A-linkage, T-compiler, C-bug, A-LTO", "label": "medium", "label_id": 2}
+{"id": "rust_152360", "text": "Issue | <!-- 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", "label": "question", "label_id": 4}
+{"id": "rust_151524", "text": "Missed optimization: introducing a temporary ownership move of `Vec` changes optimized code generation in `main`. | <!-- 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://godbolt.org/z/Ts7ss7zj4 ```rust #[no_mangle] fn grow(v: &mut Vec<isize>) {  | labels: C-optimization", "label": "medium", "label_id": 2}
+{"id": "rust_142577", "text": "Tracking Issue for reflection | This is a tracking issue for an un-RFC-ed language feature experiment The feature gate for the issue is `#![feature(reflection)]`. ### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs c | labels: T-lang, T-compiler, C-tracking-issue, S-tracking-unimplemented, B-experimental", "label": "question", "label_id": 4}
+{"id": "rust_149954", "text": "ICE: `None.unwrap()` in `tokenstream.rs` during `resolver_for_lowering_raw` | This bug was found with a fuzzer ([tree-splicer](https://github.com/langston-barrett/tree-splicer)). Reduced with [treereduce](https://github.com/langston-barrett/treereduce), then hand-reduced. [playground](https://play.rust-lang.org/?version=nightly&mode=deb | labels: I-ICE, A-parser, A-macros, T-compiler, C-bug", "label": "high", "label_id": 1}
+{"id": "rust_152374", "text": "False postive: warning of unnecessary `unsafe` block | ### Code I tried this code: ```rust fn main() { let a = unsafe { core::arch::x86_64::__cpuid_count(0, 0) }; dbg!(a); } ``` I expected to see this happen: it compiles without warnings. Instead, this happened: it compiles with a warning of unnecessary `unsafe` b | labels: T-lang, T-libs-api, C-discussion, S-has-bisection", "label": "question", "label_id": 4}
+{"id": "rust_97804", "text": "Array Repeat operator should not use a loop for small sizes | This likely caused poor assembly for `Simd::splat` in some circumstances: https://rust-lang.zulipchat.com/#narrow/stream/257879-project-portable-simd/topic/Very.20bad.20.60u16x8.3A.3Asplat.60.20codegen.20on.20x86_64 I opened a PR for a workaround: https://gith | labels: A-LLVM, I-slow, A-codegen, E-needs-test, T-compiler, A-SIMD", "label": "medium", "label_id": 2}
+{"id": "rust_55713", "text": "multiline cfg_attr in a doctest outputs a corrupted snippet | With following doctest, where the cfg attribute spans multiple lines, the final program is invalid: the wrapping `main` method doesn't take into account the dangling `stdsimd))]` line that closes the attribute. ```rust /// ```rust /// # #![cfg_attr(not(dox), f | labels: T-rustdoc, A-doctests", "label": "medium", "label_id": 2}
+{"id": "rust_114768", "text": "ICE: Failed to extract DefId: opt_local_def_id_to_hir_id | ### Code Can be reproduced by first building (in debug mode) `crates/yaboc-hir` of https://github.com/8051enthusiast/yabo at commit `442536c09df2fe898bfeda81a2788bf9dce9dc19` after a `cargo clean` and then building at commit `5d5d795041d55d3bcbe21c5052807711dd | labels: I-ICE, T-compiler, A-incr-comp, C-bug, S-has-mcve", "label": "high", "label_id": 1}
+{"id": "rust_152331", "text": "[ICE]: `arg len already exists` | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '' 'thread 'rustc' ($TID) panicked at compiler/rustc_errors/src/diagnostic.rs:359:9: 'arg len already exists'', 'thread 'rustc' ($TID) panicked at compiler/rustc_errors/src/diagnostic.rs:359:9: 'arg len already exists'' File: /t | labels: I-ICE, T-compiler, C-bug, requires-debug-assertions", "label": "high", "label_id": 1}
+{"id": "rust_149568", "text": "Method `SourceFile::normalized_byte_pos` is broken | I have been looking through the source of `rustc_span` and stumbled upon an inconsistent usage of byte positions. The problematic code is from [SourceFile::normalized_byte_pos](https://github.com/rust-lang/rust/blob/646a3f8c15baefb98dc6e0c1c1ba3356db702d2a/com | labels: T-compiler, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_152158", "text": "ICE due to RBV not handling RTN where trait is behind trait alias | Context: It's HIR ty lowering's job to resolve+lower RTN. However, it needs the lifetime resolutions from RBV which runs before HIR ty lowering and which (unfortunately) sort of duplicates some of HIR ty lowering code to resolve RTN itself. Now, while HIR ty l | labels: A-lifetimes, I-ICE, T-compiler, C-bug, F-trait_alias, S-has-mcve", "label": "high", "label_id": 1}
+{"id": "rust_152244", "text": "ICEs (in debug mode) due to RBV not expanding trait aliases when collecting bound vars from supertrait bounds | 1st reproducer: ```rs #![feature(trait_alias)] trait A<'a> { type X; } trait B: for<'a> A<'a> {} trait C = B; fn f<T>() where T: C<X: Copy> {} ``` Compiler panic message w/o backtrace: ``` thread 'rustc' (47550) panicked at compiler/rustc_type_ir/src/binder.rs | labels: I-ICE, T-compiler, C-bug, F-trait_alias, S-has-mcve, T-types", "label": "high", "label_id": 1}
+{"id": "rust_133101", "text": "Add mention that `ilog2` and `checked_ilog2` can be used to get the number of bits in an integer | ### Location - [`{integer}::ilog2`](https://doc.rust-lang.org/nightly/core/primitive.i32.html#method.ilog2) - [`{integer}::checked_ilog2`](https://doc.rust-lang.org/nightly/core/primitive.i32.html#method.checked_ilog2) - [`NonZero::ilog2`](https://doc.rust-lan | labels: A-docs, T-libs", "label": "question", "label_id": 4}
+{"id": "rust_152348", "text": "regression: parameter may not live long enough | ``` [INFO] [stdout] error[E0310]: the parameter type `T` may not live long enough [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/cogo-0.1.2/src/yield_now.rs:35:13 [INFO] [stdout] | [INFO] [stdout] 35 | let r = resour | labels: regression-from-stable-to-beta, I-prioritize", "label": "critical_bug", "label_id": 0}
+{"id": "rust_71025", "text": "Sub-optimal codegen: Unnecessarily dumping AVX registers to stack | <!-- 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 ([example 1](https://rust.godbolt.org/z/86FfSi)), in which we have a public function | labels: I-slow, C-enhancement, A-codegen, T-compiler, A-SIMD, C-optimization", "label": "low", "label_id": 3}
+{"id": "rust_152024", "text": "`unused_mut` false positive due to borrow-checking error | ### Code ```Rust struct Thing; impl Drop for Thing { fn drop(&mut self) {} } fn main() { let mut t; let mut b = None; loop { t = Thing; b.insert(&t); } } ``` ### Current output ```Shell warning: variable does not need to be mutable --> src/main.rs:7:9 | 7 | le | labels: A-lints, A-diagnostics, A-destructors, A-borrow-checker, T-compiler, L-unused_mut", "label": "medium", "label_id": 2}
+{"id": "rust_150352", "text": "Conflict markers with nonstandard lengths are not recognized as such | ### Code ```Rust <<<<<<<< ======== >>>>>>>> fn main() {} ``` ### Current output ```Shell error: expected identifier, found `<<` --> test.rs:1:1 | 1 | <<<<<<<< | ^^ expected identifier error: aborting due to 1 previous error ``` ### Desired output ```Shell erro | labels: A-diagnostics, T-compiler", "label": "low", "label_id": 3}
+{"id": "rust_141313", "text": "GVN misunderstands aliasing, can create overlapping assignments (again) | This looks very similar to https://github.com/rust-lang/rust/issues/141038, but the compiler that found this has the patch that was linked to that issue. Reduced example from rustlantis, which is accepted by Miri without optimizations enabled: ```rust #![featu | labels: P-high, T-compiler, I-unsound, C-bug, A-mir-opt, I-miscompile", "label": "high", "label_id": 1}
+{"id": "rust_127215", "text": "`*x == *y` for trait objects produce move error, so it is not equivalent to `PartialEq::eq(&*x, &*y)` even though the reference says it is | [The following code produces a move error](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=45b377544d27adffcaa1f0b38cbe22e0): ```rust trait Animal { fn noise(&self) -> String; } impl PartialEq for dyn Animal { fn eq(&self, other: &Self | labels: A-diagnostics, A-borrow-checker, T-compiler, A-docs, C-bug, A-dyn-trait", "label": "low", "label_id": 3}
+{"id": "rust_150553", "text": "`#[expect(redundant_lifetimes)]` doesn't work when `#[derive(Debug)]` is present | Consider the following code: ```rust #![deny(redundant_lifetimes)] use std::fmt::Debug; #[derive(Debug)] pub struct RefWrapper<'a, T> where 'a: 'static, T: Debug, { pub t_ref: &'a T } ``` As expected, the compiler throws an error because the `'a` lifetime is r | labels: T-lang, C-bug, I-lang-radar", "label": "medium", "label_id": 2}
+{"id": "rust_135894", "text": "Tracking Issue for `atomic_try_update` | Feature gate: `#![feature(atomic_try_update)]` This is a tracking issue for an infallible version of `AtomicT::fetch_update` as well as a new name for the existing fallible version. When and if this gets stabilized, the existing `fetch_update` should be marked | labels: T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period", "label": "question", "label_id": 4}
+{"id": "rust_138910", "text": "Linker-plugin-based LTO with -flto in clang not working | The original issue title was \"Implement cross-language ThinLTO,\" #49879 but when it was stabilized, the PR title became \"Stabilize linker-plugin based LTO (aka cross-language LTO),\" #58057 which seems to imply that fullLTO is available. The Rustc book states,  | labels: A-LLVM, T-compiler, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_151966", "text": "LLDB testing should be disabled | Per @khyperia in https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/debuginfo.20tests.20broken.20locally/with/571307617 these tests don't run in CI. On a contributor's machine they can easily fail to pass, for reasons I am not going | labels: A-testsuite, A-debuginfo, T-compiler, C-bug", "label": "low", "label_id": 3}
+{"id": "rust_136873", "text": "Tracking Issue for `cold_path` | Feature gate: `#![feature(cold_path)]` This is a tracking issue for `core::hint::{cold_path}`. Please also see the meta discussion at https://github.com/rust-lang/rust/issues/26179. `#![feature(likely_unlikely)]` was split to a new tracking issue: https://gith | labels: T-lang, T-libs-api, C-tracking-issue", "label": "question", "label_id": 4}
+{"id": "rust_26179", "text": "Meta tracking issue for branch hints (RFC 1131) | Tracking and meta discussion for branch and path hinting, including: - `likely`/`unlikely` as accepted in rust-lang/rfcs#1131 (much has changed since this RFC) - `core::hint::{likely, unlikely}` https://github.com/rust-lang/rust/issues/151619 - `core::hint::co | labels: metabug, B-RFC-approved, T-lang, B-unstable, E-help-wanted, C-tracking-issue", "label": "question", "label_id": 4}
+{"id": "rust_127031", "text": "`hir::Body`'s documentation incorrectly suggests it doesn't contain parmaeter info for closures | ### Location https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/hir/struct.Body.html ### Summary Noticed this in rust-lang/rust-clippy#12981. The documentation says \"a function\" which I assume was meant to imply both a function/method call and closure w | labels: T-compiler, A-docs", "label": "low", "label_id": 3}
+{"id": "rust_151496", "text": "Local `rustc-docs` could make use of local pages for `std` types | Posting this for @blyxyas and big thanks for having spotted this issue real quick :) ### Location (URL) The same problem persists in many different pages, just to pick an example on my machine: `$RUSTUP_HOME/toolchains/nightly-aarch64-apple-darwin/share/doc/ru | labels: T-rustdoc, A-docs", "label": "low", "label_id": 3}
+{"id": "rust_152161", "text": "Inconsistent borrow-checking and temporary lifetime behavior with async closures | I've discovered some rather strange behavior involving borrow-checking and/or temporary lifetimes of async closures. Why does it behave this way? In the snippets below, `black_box` calls are done to be really clear that const promotion isn't occurring. The fol | labels: A-borrow-checker, C-bug, A-async-closures", "label": "medium", "label_id": 2}
+{"id": "rust_152123", "text": "mGCA: Support directly represented negated literals | Follow up of #150618 and #150699. We currently support directly represented literals as a `hir::ConstArgKind::Literal` but we don't support negated literals as such a representation: ```rust #![feature(adt_const_params, min_generic_const_args)] use std::marker | labels: E-easy, E-mentor, T-compiler, A-const-generics, F-adt_const_params, T-types", "label": "question", "label_id": 4}
+{"id": "rust_138226", "text": "ICE：expected const for `N/#0` (N/#0/0) but found Type(A<N/#0>) when instantiating args=[A<N/#0>] | <!-- 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-inherent_associated_types, S-bug-has-test, requires-debug-assertions", "label": "high", "label_id": 1}
+{"id": "rust_150960", "text": "ICE: index out of bounds: the len is 0 but the index is 0 | Here is the example code that I found: ```rust #![allow(incomplete_features)] #![feature(min_generic_const_args)] pub struct A; impl A { #[type_const] const LEN: usize = 4; #[allow(unused_braces)] fn arr() -> [u8; const { Self::LEN }] { return [0u8; const { Se | labels: I-ICE, T-compiler, C-bug, S-bug-has-test, F-associated_const_equality, F-min_generic_const_args", "label": "question", "label_id": 4}
+{"id": "rust_138089", "text": "ICE: expected region but found Type | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '-Zcrate-attr=feature(generic_const_exprs) -Zcrate-attr=feature(min_generic_const_args) -Zcrate-attr=feature(inherent_associated_types) -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' panicked at /rustc/30f168ef811aec63124eac67 | labels: I-ICE, T-compiler, C-bug, F-generic_const_exprs, F-inherent_associated_types, S-bug-has-test", "label": "high", "label_id": 1}
+{"id": "rust_151027", "text": "ICE: `expected type for param #0 in [N/#0]` | <!-- 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-min_generic_const_args", "label": "high", "label_id": 1}
+{"id": "rust_151865", "text": "1.94 beta regression: \"malformed `doc` attribute input\" | The following errors are all the errors found in the 1.94 beta crater run that are related to the `doc` attribute. ## Error 1 ``` [INFO] [stdout] error[E0538]: malformed `doc` attribute input [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crat | labels: A-attributes, P-high, T-lang, T-compiler, regression-from-stable-to-beta, C-bug", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152124", "text": "mGCA: consolidate type const checks on `tcx.is_type_const` | Under `feature(min_generic_const_args)` const items have been split into two, \"const items\" and \"type const items\". Type const items are written with the `#[type_const]` attribute applied to the syntax of a normal const item. In some places in the compiler we  | labels: E-easy, C-cleanup, E-mentor, T-compiler, A-const-generics, T-types", "label": "low", "label_id": 3}
+{"id": "rust_151967", "text": "Unexpected result from recursive macro rule | <!-- 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 macro_rules! text_token { (\"{%\", $($token: literal,)*) => { println!(\"Found | labels: A-macros, C-bug, C-discussion, T-rust-analyzer", "label": "question", "label_id": 4}
+{"id": "rust_151950", "text": "unmangled symbols are not escaped in naked/global assembly | I tried this code: ```rust unsafe extern \"C\" { #[link_name = \"memset]; mov eax, 1; #\"] unsafe fn inject(); } #[unsafe(export_name = \"memset]; mov eax, 1; #\")] extern \"C\" fn inject_() {} #[unsafe(naked)] extern \"C\" fn print_0() -> usize { core::arch::naked_asm! | labels: A-codegen, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_108894", "text": "#[derive(Clone, Copy)] doesn't work | I tried this code: ```rust use std::marker::PhantomData; #[derive(Clone, Copy)] pub struct TypedAddress<T>{ inner: u64, phantom: PhantomData<T>, } pub trait Memory { fn write_value<T>(&self, offset: TypedAddress<T>, value: &T); fn return_value<T>(&self, offset | labels: A-diagnostics, A-macros, T-compiler, A-suggestion-diagnostics, D-newcomer-roadblock", "label": "medium", "label_id": 2}
+{"id": "rust_145123", "text": "Performance regression with auto-vectorization from 1.87 onwards | ### Code I tried this code: ```rust pub fn unfilter_4(previous: &[u8], current: &mut [u8]) { let mut a_bpp = [0; 4]; let mut c_bpp = [0; 4]; for (chunk, b_bpp) in current.chunks_exact_mut(4).zip(previous.chunks_exact(4)) { let new_chunk = [ chunk[0].wrapping_a | labels: A-LLVM, T-compiler, regression-from-stable-to-stable, C-bug", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152177", "text": "[ICE]: Compiler panic while compiling ppc64le rust code in linux tree | <!-- 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-PowerPC, C-bug", "label": "high", "label_id": 1}
+{"id": "rust_152026", "text": "Tracking Issue for the Soundness Criterion | This is a tracking issue for the pre-RFC [Rust Safety Standard](https://internals.rust-lang.org/t/pre-rfc-rust-safety-standard/23963). Since there is a lack of actionable guidelines for unsafe usage, we are currently working on that. We have proposed several v | labels: C-discussion", "label": "question", "label_id": 4}
+{"id": "rust_152150", "text": "Non-deterministic rmeta metadata ordering in rustc, continued, with fixes | This is a continuation of #151868 , which was locked for no good reason, and comments actually *removed*, again, for dubious reasons. Repro. script attached. [repro.sh](https://github.com/user-attachments/files/25086025/repro.sh) The prototype fix is broken in", "label": "question", "label_id": 4}
+{"id": "rust_143702", "text": "Tracking Issue for `peekable_next_if_map` | Feature gate: `#![feature(peekable_next_if_map)]` This is a tracking issue for the `std::iter::Peekable::next_if_map{_mut}` functions, as a combination of `next_if()` and transformation in a single step (ACP: rust-lang/libs-team#613). ### Public API ```rust im | labels: T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period, S-tracking-impl-incomplete", "label": "question", "label_id": 4}
+{"id": "rust_150465", "text": "regression: \"the parameter type `T` may not live long enough\" in `offset_of!` | ``` [INFO] [stdout] error[E0310]: the parameter type `T` may not live long enough [INFO] [stdout] --> src/report/data.rs:310:24 [INFO] [stdout] | [INFO] [stdout] 310 | assert_eq!(offset_of!(ReportData<T>, vtable), 0); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ | labels: P-medium, A-borrow-checker, regression-from-stable-to-beta, C-bug, finished-final-comment-period, disposition-close", "label": "critical_bug", "label_id": 0}
+{"id": "rust_147555", "text": "Tracking Issue for AArch64 FEAT_JSCVT | The feature gate for the issue is `#![feature(\"stdarch_aarch64_jscvt\")]`. # Public API This feature covers the intrinsic from the AArch64 `\"jsconv\"` target feature > Floating-point JavaScript convert to signed fixed-point, rounding toward zero ```rust #[target | labels: T-lang, T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period, A-intrinsics", "label": "question", "label_id": 4}
+{"id": "rust_122034", "text": "Tracking Issue for raw-pointer-to-reference conversion methods | <!-- 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", "label": "question", "label_id": 4}
+{"id": "rust_76654", "text": "Tracking issue for const `Pin` methods | Constify methods of `core::pin::Pin` under the feature `const_pin`. Implementation: #76655 Methods in `const_pin` (stable since 1.84.0 - https://github.com/rust-lang/rust/pull/130136): - `new` - `new_unchecked` - `get_ref` - `into_ref` - `get_mut` - `get_unche | labels: T-libs-api, A-const-eval, disposition-merge, finished-final-comment-period", "label": "medium", "label_id": 2}
+{"id": "rust_151028", "text": "ICE on nightly building futures-util | I encountered an internal compiler error when building `future-utils` on rust nightly (01/11). ### Reproduction ``` rustup toolchain install nightly git clone https://github.com/rust-lang/futures-rs.git cd futures-rs cargo +nightly doc ``` ### Meta Rust versio | labels: T-rustdoc, I-ICE, C-bug, A-intra-doc-links, regression-untriaged", "label": "high", "label_id": 1}
+{"id": "rust_136514", "text": "ICE: pattern: `attempt to add with overflow` | <!-- ICE: Rustc ./A5635DBE231F0C3535BE7A41BE7846C6C6D75F86CAE0C9F78F9847A246403528.rs '' 'thread 'rustc' panicked at compiler/rustc_mir_build/src/thir/pattern/mod.rs:237:34: 'attempt to add with overflow'', 'thread 'rustc' panicked at compiler/rustc_mir_build/ | labels: A-diagnostics, I-ICE, E-needs-test, T-compiler, C-bug, S-has-mcve", "label": "high", "label_id": 1}
+{"id": "rust_80775", "text": "Cannot build cdylib for wasm32-unknown-emscripten | Create an empty file `test.rs` and run ``` rustc -C link-args='-s SIDE_MODULE' --target wasm32-unknown-emscripten --crate-type cdylib test.rs ``` It gives the error ``` error: linking with `emcc` failed: exit code: 1 | = note: \"emcc\" \"-s\" \"DISABLE_EXCEPTION_CA | labels: O-wasm, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_149945", "text": "Avoid monomorphizing intrinsic fallback bodies that the backend does not need | Currently, when an intrinsic with a fallback body gets used, we always monomorphize and codegen that body: mono item collection does not know whether the backend will invoke the fallback body or supply its own implementation. This has led to perf regressions i | labels: I-compiletime, T-compiler", "label": "high", "label_id": 1}
+{"id": "rust_71009", "text": "De-stabilize target spec JSON | In a recent [Zulip discussion](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Stability.20guarantees.20of.20custom.20target.20specifications), it was noted that we currently consider JSON target specifications unstable, in the sense tha | labels: A-stability, T-compiler, A-target-specs, C-discussion", "label": "question", "label_id": 4}
+{"id": "rust_98338", "text": "Current handling of Unix close() can lead to silent data loss | While working on #98209 , I went searching for where close() is called. I found it in std/src/os/fd/owned.rs: ``` impl Drop for OwnedFd { #[inline] fn drop(&mut self) { unsafe { // Note that errors are ignored when closing a file descriptor. The // reason for  | labels: T-libs-api, C-bug, A-io", "label": "medium", "label_id": 2}
+{"id": "rust_137582", "text": "ICE: `assertion failed: layout.is_sized()` with `feature(adt_const_params)` | <!-- 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: E-easy, I-ICE, E-mentor, T-compiler, C-bug, F-adt_const_params", "label": "high", "label_id": 1}
+{"id": "rust_151610", "text": "[ICE]: `Span must not be empty and have no suggestion` | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '-Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_errors/src/diagnostic.rs:998:9: 'Span must not be empty and have no suggestion'', 'thread 'rustc' ($TID) panicked at comp | labels: A-diagnostics, I-ICE, T-compiler, C-bug, requires-debug-assertions, WG-trait-system-refactor", "label": "high", "label_id": 1}
+{"id": "rust_101169", "text": "unreachable_pub lint false positive | <!-- 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 #![warn(unreachable_pub)] mod foo { pub struct Foo; } use foo::Foo; ``` [He | labels: A-lints, C-bug, L-unreachable_pub", "label": "medium", "label_id": 2}
+{"id": "rust_152078", "text": "Potential in-module UB in alloc | `HOOK` is a static variable: https://github.com/rust-lang/rust/blob/5ac8ecea36e7548534e0bc3d4aa1c12bd4908566/library/std/src/alloc.rs#L297 `rust_oom` transmutes a pointer `hook` obtained from HOOK into a function: https://github.com/rust-lang/rust/blob/5ac8ece | labels: C-bug, T-libs", "label": "critical_bug", "label_id": 0}
+{"id": "rust_148470", "text": "Partial pointers in padding can make const-eval fail | I'm not sure if this is a bug or not. ```rust #![allow(unused)] #[repr(C, align(16))] #[derive(Clone, Copy)] struct Thing { x: u128, y: u64, // Replace the above line with the below line to make it stop compiling // y: std::mem::MaybeUninit<u64>, // 8 bytes of | labels: T-lang, T-compiler, C-bug, A-const-eval, A-ABI, T-opsem", "label": "question", "label_id": 4}
+{"id": "rust_151591", "text": "[ICE]: assertion failed: layout.is_sized() | <!-- 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", "label": "high", "label_id": 1}
+{"id": "rust_151708", "text": "[ICE]: generics_of: unexpected node kind Crate(Mod | <!-- \u001b[31mICE\u001b[0m: Rustc ./18074FF2C0026A2CB1DAE74699BC86DCF7076BEED1E87DC391BFFFB43561B701.rs '-Zcrate-attr=feature(min_generic_const_args) -ooutputfile -Zdump-mir-dir=dir' 'error: internal compiler error: compiler/rustc_hir_analysis/src/collect/generics_of.r | labels: I-ICE, T-compiler, C-bug, F-min_generic_const_args", "label": "high", "label_id": 1}
+{"id": "rust_147339", "text": "ICE: `span context mismatch` | <!-- \u001b[31mICE\u001b[0m: Rustc ./meta-variable-misuse.rs '-Cinstrument-coverage -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_mir_transform/src/coverage/spans.rs:56:13: 'span context mismatch: body_span=/tmp/im/meta-variable-misu | labels: I-ICE, T-compiler, C-bug, A-code-coverage, requires-debug-assertions", "label": "high", "label_id": 1}
+{"id": "rust_152062", "text": "Deriving Default for non-default generics should work in trivial cases | <!-- 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. --> ```rust struct NoDefault {} #[derive(Default)] struct VecHolder<T> { data: Vec<T>, } fn main() { let x | labels: C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_151643", "text": "rustc `--color always` doesn't always output color | Zulip discussion: [#t-compiler > Rustc &#96;--color always&#96; doesn't always color output](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Rustc.20.60--color.20always.60.20doesn't.20always.20color.20output/with/568526766) While workin | labels: A-diagnostics, T-compiler, C-bug, D-inconsistent, A-error-codes", "label": "question", "label_id": 4}
+{"id": "rust_152043", "text": "Miscompilation with vectors | I tried this code: ```rust use std::ops::{Add, Mul}; #[derive(Copy, Clone, Debug, Hash, PartialEq, Eq)] pub struct Vector2<S> { pub x: S, pub y: S, } impl<S> Add<Vector2<S>> for Vector2<S> where S: Add<Output = S> + Copy, { type Output = Vector2<S>; fn add(sel | labels: C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_127643", "text": "ICE: `assertion failed: layout.is_sized()` with `feature(associated_const_equality)` | <!-- 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, E-needs-test, T-compiler, C-bug, A-layout, F-associated_const_equality", "label": "high", "label_id": 1}
+{"id": "rust_151996", "text": "diagnostic::do_not_recommend can emit an error if it encounters a keyword | <!-- 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 #![crate_type = \"lib\"] pub trait X{} pub struct Y; #[diagnostic::do_not_rec | labels: A-attributes, T-compiler, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_151983", "text": "Missing \"unused variable\" warning when using a match guard | <!-- 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 fn main() { match Some(42) { Some(unused) if true => (), _ => (), } } ``` I | labels: A-lints, P-medium, T-compiler, regression-from-stable-to-stable, C-bug, L-unused_variables", "label": "critical_bug", "label_id": 0}
+{"id": "rust_142519", "text": "Function no longer auto-vectorizes in 1.87.0 | <!-- Thank you for filing a regression report! 🐛 A regression is something that changed between versions of Rust but was not supposed to. Please provide a short summary of the regression, along with any information you feel is relevant to replicate it. --> ### | labels: A-LLVM, I-slow, E-needs-test, P-high, T-compiler, regression-from-stable-to-stable", "label": "critical_bug", "label_id": 0}
+{"id": "rust_85532", "text": "Tracking Issue for bigint helper methods | <!-- 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", "label": "question", "label_id": 4}
+{"id": "rust_151607", "text": "[ICE]: ` all spans must be disjoint` | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '' 'assertion `left == right` failed: all spans must be disjoint ' left: Some([SubstitutionPart { span: /tmp/im/2/a.rs:5:13: 5:16 (#0), snippet: \"\" }, SubstitutionPart { span: /tmp/im/2/a.rs:5:15: 5:16 (#0), snippet: \"/* e */\" } | labels: A-diagnostics, I-ICE, T-compiler, C-bug, requires-debug-assertions", "label": "high", "label_id": 1}
+{"id": "rust_147265", "text": "Rust 1.90 compiler optimization (O2, O3) triggers UB with Box::from_raw() | ### Code I minimized the issue to the following testcase, which uses serde and `bincode` to serialize a structure by boxing it, serializing the exposed address and reconstructs the box from the deserialized address. I believe this to be valid, as long as one c | labels: A-LLVM, P-medium, T-compiler, regression-from-stable-to-stable, C-bug, T-opsem", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151088", "text": "Alarming memory use and non-termination. | I cloned the [rust serialization benchmark repository](https://github.com/djkoloski/rust_serialization_benchmark/), which I have been able to `cargo bench`. I made a modification, to use a local checkout of the `columnar` crate, with this diff ``` mcsherry@gal | labels: A-LLVM, I-compiletime, P-high, T-compiler, regression-from-stable-to-stable, C-bug", "label": "question", "label_id": 4}
+{"id": "rust_152007", "text": "rustdoc should have some indication of hidden bounds | If you look at <https://doc.rust-lang.org/nightly/std/ops/struct.RangeInclusive.html#impl-Iterator-for-RangeInclusive%3CA%3E>, for example, it appears as though `RangeInclusive<A>: Iterator` holds *for all `A`*. That's not the case, however, because there's a  | labels: T-rustdoc, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_129004", "text": "`if let` not possible in short-hand syntax? | labels: A-diagnostics, C-discussion", "label": "question", "label_id": 4}
+{"id": "rust_151941", "text": "Possible AVX2-only performance regression (again). | Hello! Seems I can reproduce a **very similar AVX2-only performance regression** (stable-to-stable) to the one described in the `image-png` issue here: - https://github.com/image-rs/image-png/issues/598 ## Repository / code - Repo: https://github.com/sherman/b | labels: C-bug, regression-untriaged, perf-regression", "label": "high", "label_id": 1}
+{"id": "rust_151878", "text": "[ICE]: `expected Binder to have 1 projections, but it has 0` | <!-- \u001b[31mICE\u001b[0m: Rustc ./dyn-compat-self-const-projections-in-methods.rs '-Zsanitizer=cfi -Ccodegen-units=1 -Clto -Cunsafe-allow-abi-mismatch=sanitizer -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_middle/src/ty/sty.rs:73 | labels: I-ICE, T-compiler, C-bug, requires-debug-assertions, F-min_generic_const_args, A-control-flow-integrity", "label": "high", "label_id": 1}
+{"id": "rust_151331", "text": "[ICE]: `expected a projection` | <!-- \u001b[31mICE\u001b[0m: Rustc ./DC87D749F7189DB6749EB7B0F246583DCA01BDEC0317D86213F29E3CDF421FE8.rs '-Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_type_ir/src/predicate.rs:689:9: 'expected a projection'',  | labels: I-ICE, T-compiler, C-bug, F-type_alias_impl_trait, S-has-mcve, WG-trait-system-refactor", "label": "high", "label_id": 1}
+{"id": "rust_138225", "text": "ICE：called `Result::unwrap()` on an `Err` value: ReferencesError(ErrorGuaranteed(())) | **Similar to problem #128094, it may be a duplicate problem, but the compile command is different The issue compilation command I opened is `-C opt-level=1`, and #128094 is `-Zmir-opt-level=5 --edition=2018`** And the code is a little different, so I brought u | labels: I-ICE, E-needs-test, T-compiler, C-bug, A-mir-opt", "label": "high", "label_id": 1}
+{"id": "rust_151728", "text": "Sorting Boxes causes Miri to report UB | This issue was discovered by @orxfun on [zulip](https://rust-lang.zulipchat.com/#narrow/channel/269128-miri/topic/miri.20fails.20when.20sorting.20slice.20of.20boxed.20integers/with/570245641). The following code causes Miri to report UB: ```rust fn main() { // | labels: P-high, regression-from-stable-to-stable, I-unsound, C-bug, T-libs, T-opsem", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151951", "text": "[ICE]: Latest rust cannot build ans1-rs | <!-- 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", "label": "high", "label_id": 1}
+{"id": "rust_151868", "text": "Non-deterministic rmeta metadata ordering in rustc 1.95.0-nightly | # Non-deterministic rmeta metadata ordering persists in rustc 1.95.0-nightly ## Summary Building the same crate twice with identical inputs produces `.rlib` files with different hashes due to non-deterministic ordering in `lib.rmeta`. The compiled object code  | labels: T-compiler, C-bug, S-needs-repro", "label": "medium", "label_id": 2}
+{"id": "rust_94691", "text": "Document FAQ why we have both PartialEq and Eq in PartialEq | The title says it all. It's a frequently asked question; most recently on [reddit](https://www.reddit.com/r/rust/comments/t8d6wb/why_does_rust_have_eq_and_partialeq/). It'd be nice if we could link to the standard library docs to answer this. | labels: A-docs, T-libs", "label": "question", "label_id": 4}
+{"id": "rust_151846", "text": "unused_allocation warning should ignore allocations to pass Box to things taking self: &Box | ### Code ```Rust // Copyright 2026 Google LLC. // SPDX-License-Identifier: Apache-2.0 struct MyStruct; trait TraitTakesBoxRef { fn trait_takes_box_ref(&self); } impl TraitTakesBoxRef for Box<MyStruct> { fn trait_takes_box_ref(&self) {} } impl MyStruct { fn inh | labels: A-diagnostics, T-compiler, L-unused_allocation", "label": "medium", "label_id": 2}
+{"id": "rust_151882", "text": "[ICE]: frontmatter: begin <= end (4 <= 0) when slicing `----` | <!-- \u001b[31mICE\u001b[0m: Rustc ./code.rs '' 'thread 'rustc' ($TID) panicked at compiler/rustc_parse/src/lexer/mod.rs:628:30: 'begin <= end (4 <= 0) when slicing `----`'', 'thread 'rustc' ($TID) panicked at compiler/rustc_parse/src/lexer/mod.rs:628:30: 'begin <= end  | labels: I-ICE, T-compiler, C-bug, S-has-mcve, F-frontmatter", "label": "high", "label_id": 1}
+{"id": "rust_117216", "text": "Tracking Issue for AArch64 TME intrinsics | <!-- 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, O-AArch64", "label": "question", "label_id": 4}
+{"id": "rust_146842", "text": "rust 1.90.0, 1.91.0 and 1.92.0 on big-endian aarch64 all fail with \"internal error: entered unreachable code: found `99`\" | As mentioned in issue #145230, rust 1.90.0 can now be cross-built for the `aarch64_be-unknown-netbsd` target. However, trying to use the result to build e.g. `dua-cli` (ref. https://github.com/Byron/dua-cli/), fails on the first invocation of the rust compiler | labels: I-ICE, T-compiler, C-bug, A-targets, E-needs-investigation", "label": "high", "label_id": 1}
+{"id": "rust_119905", "text": "-Znext-solver=coherence: stack overflow | <!-- 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-compiler, C-bug, I-hang, WG-trait-system-refactor", "label": "high", "label_id": 1}
+{"id": "rust_147825", "text": "Unstable fingerprints in `evaluate_obligation` | ### Code https://github.com/Noratrieb/evaluate_obligation-fingerprints All credits for running into this and creating an initial reproduction and minimization goes to @muja via the Rust Community Discord, I just picked it up and continued minimizing it. This i | labels: I-ICE, T-compiler, A-incr-comp, C-bug", "label": "high", "label_id": 1}
+{"id": "rust_151090", "text": "checksum-freshness: does not work with binary embedded files | <!-- 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 with `-Zchecksum-freshness` enabled on cargo side: ```rust // random_bytes have to b | labels: T-compiler, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_151855", "text": "Failure when compiling rustc due to file permissions in /usr | ### Summary I'm compiling rustc in an openSUSE docker container. When running `make` I very quickly get an error because it's trying to copy `/usr` to `stage0-sysroot`. The file in question is this one: ```sh -rwsr-x--- 1 root messagebus 56K Jun 20 2023 /usr/l | labels: T-bootstrap, C-bug", "label": "question", "label_id": 4}

train_labeled.jsonl

@@ -0,0 +1,100 @@
+{"id": "rust_150179", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152771", "text": "[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", "label": "question", "label_id": 4}
+{"id": "rust_151729", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_152585", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_97270", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152501", "text": "`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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152601", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_152692", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_152518", "text": "[ICE]: fulfillment_errors: index out of bounds: the len is 1 but the index is 1 | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_131891", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_148203", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_128933", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_152719", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_152079", "text": "`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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_141726", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_133469", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_148730", "text": "ICE `type_of` called on const argument's anon const before the const argument was lowered | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_53667", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_104893", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_151647", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_135974", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_152588", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_115336", "text": "`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", "label": "high", "label_id": 1}
+{"id": "rust_150018", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_141738", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_152493", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_152263", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_76001", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_59490", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_60471", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152030", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_142152", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_133966", "text": "ICE: `expected wide pointer extra data (e.g. slice length or trait object vtable)` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_150983", "text": "ICE: `ty::ConstKind::Error constructed but no error reported` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_151625", "text": "[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", "label": "question", "label_id": 4}
+{"id": "rust_152354", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_146803", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_142394", "text": "`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", "label": "medium", "label_id": 2}
+{"id": "rust_146590", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152545", "text": "[ICE]: `invalid rigid alias in layout_of after normalization` | <!-- \u001b[31mICE\u001b[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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_73321", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_152014", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_148854", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_115175", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152539", "text": "`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", "label": "question", "label_id": 4}
+{"id": "rust_151330", "text": "[ICE]: vtable : `None` from `prepare_vtable_segments()` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_151414", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_148953", "text": "ICE unexpected `DefKind` for const alias to resolve to: `Ctor(Struct, Const)` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_135845", "text": "ICE: `cannot convert ReLateParam to a region vid` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_152499", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152231", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_152470", "text": "[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", "label": "low", "label_id": 3}
+{"id": "rust_150899", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_104463", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_152510", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_147465", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_145866", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_128203", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_147370", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_148372", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_151807", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_148738", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_71043", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_143531", "text": "`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", "label": "medium", "label_id": 2}
+{"id": "rust_151832", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_71850", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_49569", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152347", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151124", "text": "ICE: `DefId(..)): reachable Public > nominal Restricted(DefId(..)` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_152004", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_151791", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152482", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_74756", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_151904", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_147883", "text": "\"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", "label": "high", "label_id": 1}
+{"id": "rust_115399", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_122620", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_141679", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_81059", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_82775", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_151705", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_151818", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151926", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152255", "text": "\"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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_124309", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_88051", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152468", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_152467", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_151358", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_152464", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152453", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_142778", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_141540", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_111164", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_109829", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_143358", "text": "ICE: `unhandled node ConstArg(ConstArg ` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_131292", "text": "ICE: `bpos.to_u32() >= mbc.pos.to_u32() + mbc.bytes as u32` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_152376", "text": "`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", "label": "question", "label_id": 4}
+{"id": "rust_151273", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_80317", "text": "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", "label": "medium", "label_id": 2}

unlabeled_pool.jsonl

@@ -0,0 +1,100 @@
+{"id": "rust_152026", "text": "Tracking Issue for the Soundness Criterion | This is a tracking issue for the pre-RFC [Rust Safety Standard](https://internals.rust-lang.org/t/pre-rfc-rust-safety-standard/23963). Since there is a lack of actionable guidelines for unsafe usage, we are currently working on that. We have proposed several v | labels: C-discussion"}
+{"id": "rust_152150", "text": "Non-deterministic rmeta metadata ordering in rustc, continued, with fixes | This is a continuation of #151868 , which was locked for no good reason, and comments actually *removed*, again, for dubious reasons. Repro. script attached. [repro.sh](https://github.com/user-attachments/files/25086025/repro.sh) The prototype fix is broken in"}
+{"id": "rust_143702", "text": "Tracking Issue for `peekable_next_if_map` | Feature gate: `#![feature(peekable_next_if_map)]` This is a tracking issue for the `std::iter::Peekable::next_if_map{_mut}` functions, as a combination of `next_if()` and transformation in a single step (ACP: rust-lang/libs-team#613). ### Public API ```rust im | labels: T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period, S-tracking-impl-incomplete"}
+{"id": "rust_150465", "text": "regression: \"the parameter type `T` may not live long enough\" in `offset_of!` | ``` [INFO] [stdout] error[E0310]: the parameter type `T` may not live long enough [INFO] [stdout] --> src/report/data.rs:310:24 [INFO] [stdout] | [INFO] [stdout] 310 | assert_eq!(offset_of!(ReportData<T>, vtable), 0); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ | labels: P-medium, A-borrow-checker, regression-from-stable-to-beta, C-bug, finished-final-comment-period, disposition-close"}
+{"id": "rust_147555", "text": "Tracking Issue for AArch64 FEAT_JSCVT | The feature gate for the issue is `#![feature(\"stdarch_aarch64_jscvt\")]`. # Public API This feature covers the intrinsic from the AArch64 `\"jsconv\"` target feature > Floating-point JavaScript convert to signed fixed-point, rounding toward zero ```rust #[target | labels: T-lang, T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period, A-intrinsics"}
+{"id": "rust_122034", "text": "Tracking Issue for raw-pointer-to-reference conversion methods | <!-- 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"}
+{"id": "rust_76654", "text": "Tracking issue for const `Pin` methods | Constify methods of `core::pin::Pin` under the feature `const_pin`. Implementation: #76655 Methods in `const_pin` (stable since 1.84.0 - https://github.com/rust-lang/rust/pull/130136): - `new` - `new_unchecked` - `get_ref` - `into_ref` - `get_mut` - `get_unche | labels: T-libs-api, A-const-eval, disposition-merge, finished-final-comment-period"}
+{"id": "rust_151028", "text": "ICE on nightly building futures-util | I encountered an internal compiler error when building `future-utils` on rust nightly (01/11). ### Reproduction ``` rustup toolchain install nightly git clone https://github.com/rust-lang/futures-rs.git cd futures-rs cargo +nightly doc ``` ### Meta Rust versio | labels: T-rustdoc, I-ICE, C-bug, A-intra-doc-links, regression-untriaged"}
+{"id": "rust_136514", "text": "ICE: pattern: `attempt to add with overflow` | <!-- ICE: Rustc ./A5635DBE231F0C3535BE7A41BE7846C6C6D75F86CAE0C9F78F9847A246403528.rs '' 'thread 'rustc' panicked at compiler/rustc_mir_build/src/thir/pattern/mod.rs:237:34: 'attempt to add with overflow'', 'thread 'rustc' panicked at compiler/rustc_mir_build/ | labels: A-diagnostics, I-ICE, E-needs-test, T-compiler, C-bug, S-has-mcve"}
+{"id": "rust_80775", "text": "Cannot build cdylib for wasm32-unknown-emscripten | Create an empty file `test.rs` and run ``` rustc -C link-args='-s SIDE_MODULE' --target wasm32-unknown-emscripten --crate-type cdylib test.rs ``` It gives the error ``` error: linking with `emcc` failed: exit code: 1 | = note: \"emcc\" \"-s\" \"DISABLE_EXCEPTION_CA | labels: O-wasm, C-bug"}
+{"id": "rust_149945", "text": "Avoid monomorphizing intrinsic fallback bodies that the backend does not need | Currently, when an intrinsic with a fallback body gets used, we always monomorphize and codegen that body: mono item collection does not know whether the backend will invoke the fallback body or supply its own implementation. This has led to perf regressions i | labels: I-compiletime, T-compiler"}
+{"id": "rust_71009", "text": "De-stabilize target spec JSON | In a recent [Zulip discussion](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Stability.20guarantees.20of.20custom.20target.20specifications), it was noted that we currently consider JSON target specifications unstable, in the sense tha | labels: A-stability, T-compiler, A-target-specs, C-discussion"}
+{"id": "rust_98338", "text": "Current handling of Unix close() can lead to silent data loss | While working on #98209 , I went searching for where close() is called. I found it in std/src/os/fd/owned.rs: ``` impl Drop for OwnedFd { #[inline] fn drop(&mut self) { unsafe { // Note that errors are ignored when closing a file descriptor. The // reason for  | labels: T-libs-api, C-bug, A-io"}
+{"id": "rust_137582", "text": "ICE: `assertion failed: layout.is_sized()` with `feature(adt_const_params)` | <!-- 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: E-easy, I-ICE, E-mentor, T-compiler, C-bug, F-adt_const_params"}
+{"id": "rust_151610", "text": "[ICE]: `Span must not be empty and have no suggestion` | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '-Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_errors/src/diagnostic.rs:998:9: 'Span must not be empty and have no suggestion'', 'thread 'rustc' ($TID) panicked at comp | labels: A-diagnostics, I-ICE, T-compiler, C-bug, requires-debug-assertions, WG-trait-system-refactor"}
+{"id": "rust_101169", "text": "unreachable_pub lint false positive | <!-- 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 #![warn(unreachable_pub)] mod foo { pub struct Foo; } use foo::Foo; ``` [He | labels: A-lints, C-bug, L-unreachable_pub"}
+{"id": "rust_152078", "text": "Potential in-module UB in alloc | `HOOK` is a static variable: https://github.com/rust-lang/rust/blob/5ac8ecea36e7548534e0bc3d4aa1c12bd4908566/library/std/src/alloc.rs#L297 `rust_oom` transmutes a pointer `hook` obtained from HOOK into a function: https://github.com/rust-lang/rust/blob/5ac8ece | labels: C-bug, T-libs"}
+{"id": "rust_148470", "text": "Partial pointers in padding can make const-eval fail | I'm not sure if this is a bug or not. ```rust #![allow(unused)] #[repr(C, align(16))] #[derive(Clone, Copy)] struct Thing { x: u128, y: u64, // Replace the above line with the below line to make it stop compiling // y: std::mem::MaybeUninit<u64>, // 8 bytes of | labels: T-lang, T-compiler, C-bug, A-const-eval, A-ABI, T-opsem"}
+{"id": "rust_151591", "text": "[ICE]: assertion failed: layout.is_sized() | <!-- 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"}
+{"id": "rust_151708", "text": "[ICE]: generics_of: unexpected node kind Crate(Mod | <!-- \u001b[31mICE\u001b[0m: Rustc ./18074FF2C0026A2CB1DAE74699BC86DCF7076BEED1E87DC391BFFFB43561B701.rs '-Zcrate-attr=feature(min_generic_const_args) -ooutputfile -Zdump-mir-dir=dir' 'error: internal compiler error: compiler/rustc_hir_analysis/src/collect/generics_of.r | labels: I-ICE, T-compiler, C-bug, F-min_generic_const_args"}
+{"id": "rust_147339", "text": "ICE: `span context mismatch` | <!-- \u001b[31mICE\u001b[0m: Rustc ./meta-variable-misuse.rs '-Cinstrument-coverage -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_mir_transform/src/coverage/spans.rs:56:13: 'span context mismatch: body_span=/tmp/im/meta-variable-misu | labels: I-ICE, T-compiler, C-bug, A-code-coverage, requires-debug-assertions"}
+{"id": "rust_152062", "text": "Deriving Default for non-default generics should work in trivial cases | <!-- 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. --> ```rust struct NoDefault {} #[derive(Default)] struct VecHolder<T> { data: Vec<T>, } fn main() { let x | labels: C-bug"}
+{"id": "rust_151643", "text": "rustc `--color always` doesn't always output color | Zulip discussion: [#t-compiler > Rustc &#96;--color always&#96; doesn't always color output](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Rustc.20.60--color.20always.60.20doesn't.20always.20color.20output/with/568526766) While workin | labels: A-diagnostics, T-compiler, C-bug, D-inconsistent, A-error-codes"}
+{"id": "rust_152043", "text": "Miscompilation with vectors | I tried this code: ```rust use std::ops::{Add, Mul}; #[derive(Copy, Clone, Debug, Hash, PartialEq, Eq)] pub struct Vector2<S> { pub x: S, pub y: S, } impl<S> Add<Vector2<S>> for Vector2<S> where S: Add<Output = S> + Copy, { type Output = Vector2<S>; fn add(sel | labels: C-bug"}
+{"id": "rust_127643", "text": "ICE: `assertion failed: layout.is_sized()` with `feature(associated_const_equality)` | <!-- 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, E-needs-test, T-compiler, C-bug, A-layout, F-associated_const_equality"}
+{"id": "rust_151996", "text": "diagnostic::do_not_recommend can emit an error if it encounters a keyword | <!-- 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 #![crate_type = \"lib\"] pub trait X{} pub struct Y; #[diagnostic::do_not_rec | labels: A-attributes, T-compiler, C-bug"}
+{"id": "rust_151983", "text": "Missing \"unused variable\" warning when using a match guard | <!-- 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 fn main() { match Some(42) { Some(unused) if true => (), _ => (), } } ``` I | labels: A-lints, P-medium, T-compiler, regression-from-stable-to-stable, C-bug, L-unused_variables"}
+{"id": "rust_142519", "text": "Function no longer auto-vectorizes in 1.87.0 | <!-- Thank you for filing a regression report! 🐛 A regression is something that changed between versions of Rust but was not supposed to. Please provide a short summary of the regression, along with any information you feel is relevant to replicate it. --> ### | labels: A-LLVM, I-slow, E-needs-test, P-high, T-compiler, regression-from-stable-to-stable"}
+{"id": "rust_85532", "text": "Tracking Issue for bigint helper methods | <!-- 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"}
+{"id": "rust_151607", "text": "[ICE]: ` all spans must be disjoint` | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '' 'assertion `left == right` failed: all spans must be disjoint ' left: Some([SubstitutionPart { span: /tmp/im/2/a.rs:5:13: 5:16 (#0), snippet: \"\" }, SubstitutionPart { span: /tmp/im/2/a.rs:5:15: 5:16 (#0), snippet: \"/* e */\" } | labels: A-diagnostics, I-ICE, T-compiler, C-bug, requires-debug-assertions"}
+{"id": "rust_147265", "text": "Rust 1.90 compiler optimization (O2, O3) triggers UB with Box::from_raw() | ### Code I minimized the issue to the following testcase, which uses serde and `bincode` to serialize a structure by boxing it, serializing the exposed address and reconstructs the box from the deserialized address. I believe this to be valid, as long as one c | labels: A-LLVM, P-medium, T-compiler, regression-from-stable-to-stable, C-bug, T-opsem"}
+{"id": "rust_151088", "text": "Alarming memory use and non-termination. | I cloned the [rust serialization benchmark repository](https://github.com/djkoloski/rust_serialization_benchmark/), which I have been able to `cargo bench`. I made a modification, to use a local checkout of the `columnar` crate, with this diff ``` mcsherry@gal | labels: A-LLVM, I-compiletime, P-high, T-compiler, regression-from-stable-to-stable, C-bug"}
+{"id": "rust_152007", "text": "rustdoc should have some indication of hidden bounds | If you look at <https://doc.rust-lang.org/nightly/std/ops/struct.RangeInclusive.html#impl-Iterator-for-RangeInclusive%3CA%3E>, for example, it appears as though `RangeInclusive<A>: Iterator` holds *for all `A`*. That's not the case, however, because there's a  | labels: T-rustdoc, C-bug"}
+{"id": "rust_129004", "text": "`if let` not possible in short-hand syntax? | labels: A-diagnostics, C-discussion"}
+{"id": "rust_151941", "text": "Possible AVX2-only performance regression (again). | Hello! Seems I can reproduce a **very similar AVX2-only performance regression** (stable-to-stable) to the one described in the `image-png` issue here: - https://github.com/image-rs/image-png/issues/598 ## Repository / code - Repo: https://github.com/sherman/b | labels: C-bug, regression-untriaged, perf-regression"}
+{"id": "rust_151878", "text": "[ICE]: `expected Binder to have 1 projections, but it has 0` | <!-- \u001b[31mICE\u001b[0m: Rustc ./dyn-compat-self-const-projections-in-methods.rs '-Zsanitizer=cfi -Ccodegen-units=1 -Clto -Cunsafe-allow-abi-mismatch=sanitizer -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_middle/src/ty/sty.rs:73 | labels: I-ICE, T-compiler, C-bug, requires-debug-assertions, F-min_generic_const_args, A-control-flow-integrity"}
+{"id": "rust_151331", "text": "[ICE]: `expected a projection` | <!-- \u001b[31mICE\u001b[0m: Rustc ./DC87D749F7189DB6749EB7B0F246583DCA01BDEC0317D86213F29E3CDF421FE8.rs '-Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_type_ir/src/predicate.rs:689:9: 'expected a projection'',  | labels: I-ICE, T-compiler, C-bug, F-type_alias_impl_trait, S-has-mcve, WG-trait-system-refactor"}
+{"id": "rust_138225", "text": "ICE：called `Result::unwrap()` on an `Err` value: ReferencesError(ErrorGuaranteed(())) | **Similar to problem #128094, it may be a duplicate problem, but the compile command is different The issue compilation command I opened is `-C opt-level=1`, and #128094 is `-Zmir-opt-level=5 --edition=2018`** And the code is a little different, so I brought u | labels: I-ICE, E-needs-test, T-compiler, C-bug, A-mir-opt"}
+{"id": "rust_151728", "text": "Sorting Boxes causes Miri to report UB | This issue was discovered by @orxfun on [zulip](https://rust-lang.zulipchat.com/#narrow/channel/269128-miri/topic/miri.20fails.20when.20sorting.20slice.20of.20boxed.20integers/with/570245641). The following code causes Miri to report UB: ```rust fn main() { // | labels: P-high, regression-from-stable-to-stable, I-unsound, C-bug, T-libs, T-opsem"}
+{"id": "rust_151951", "text": "[ICE]: Latest rust cannot build ans1-rs | <!-- 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"}
+{"id": "rust_151868", "text": "Non-deterministic rmeta metadata ordering in rustc 1.95.0-nightly | # Non-deterministic rmeta metadata ordering persists in rustc 1.95.0-nightly ## Summary Building the same crate twice with identical inputs produces `.rlib` files with different hashes due to non-deterministic ordering in `lib.rmeta`. The compiled object code  | labels: T-compiler, C-bug, S-needs-repro"}
+{"id": "rust_94691", "text": "Document FAQ why we have both PartialEq and Eq in PartialEq | The title says it all. It's a frequently asked question; most recently on [reddit](https://www.reddit.com/r/rust/comments/t8d6wb/why_does_rust_have_eq_and_partialeq/). It'd be nice if we could link to the standard library docs to answer this. | labels: A-docs, T-libs"}
+{"id": "rust_151846", "text": "unused_allocation warning should ignore allocations to pass Box to things taking self: &Box | ### Code ```Rust // Copyright 2026 Google LLC. // SPDX-License-Identifier: Apache-2.0 struct MyStruct; trait TraitTakesBoxRef { fn trait_takes_box_ref(&self); } impl TraitTakesBoxRef for Box<MyStruct> { fn trait_takes_box_ref(&self) {} } impl MyStruct { fn inh | labels: A-diagnostics, T-compiler, L-unused_allocation"}
+{"id": "rust_151882", "text": "[ICE]: frontmatter: begin <= end (4 <= 0) when slicing `----` | <!-- \u001b[31mICE\u001b[0m: Rustc ./code.rs '' 'thread 'rustc' ($TID) panicked at compiler/rustc_parse/src/lexer/mod.rs:628:30: 'begin <= end (4 <= 0) when slicing `----`'', 'thread 'rustc' ($TID) panicked at compiler/rustc_parse/src/lexer/mod.rs:628:30: 'begin <= end  | labels: I-ICE, T-compiler, C-bug, S-has-mcve, F-frontmatter"}
+{"id": "rust_117216", "text": "Tracking Issue for AArch64 TME intrinsics | <!-- 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, O-AArch64"}
+{"id": "rust_146842", "text": "rust 1.90.0, 1.91.0 and 1.92.0 on big-endian aarch64 all fail with \"internal error: entered unreachable code: found `99`\" | As mentioned in issue #145230, rust 1.90.0 can now be cross-built for the `aarch64_be-unknown-netbsd` target. However, trying to use the result to build e.g. `dua-cli` (ref. https://github.com/Byron/dua-cli/), fails on the first invocation of the rust compiler | labels: I-ICE, T-compiler, C-bug, A-targets, E-needs-investigation"}
+{"id": "rust_119905", "text": "-Znext-solver=coherence: stack overflow | <!-- 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-compiler, C-bug, I-hang, WG-trait-system-refactor"}
+{"id": "rust_147825", "text": "Unstable fingerprints in `evaluate_obligation` | ### Code https://github.com/Noratrieb/evaluate_obligation-fingerprints All credits for running into this and creating an initial reproduction and minimization goes to @muja via the Rust Community Discord, I just picked it up and continued minimizing it. This i | labels: I-ICE, T-compiler, A-incr-comp, C-bug"}
+{"id": "rust_151090", "text": "checksum-freshness: does not work with binary embedded files | <!-- 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 with `-Zchecksum-freshness` enabled on cargo side: ```rust // random_bytes have to b | labels: T-compiler, C-bug"}
+{"id": "rust_151855", "text": "Failure when compiling rustc due to file permissions in /usr | ### Summary I'm compiling rustc in an openSUSE docker container. When running `make` I very quickly get an error because it's trying to copy `/usr` to `stage0-sysroot`. The file in question is this one: ```sh -rwsr-x--- 1 root messagebus 56K Jun 20 2023 /usr/l | labels: T-bootstrap, C-bug"}
+{"id": "rust_150896", "text": "std's tests fail to dynamically link under Windows 7 due to `GetHostNameW` missing | When running `std`'s tests under Windows 7, it fails on the first execution on the following error: ``` Running unittests lib.rs (build/x86_64-unknown-linux-gnu/stage1-std/x86_64-win7-windows-msvc/release/deps/alloctests-6f6372787480eb2d.exe) uploaded \"/builds | labels: C-bug, T-libs, A-io, O-windows-7"}
+{"id": "rust_149829", "text": "Tracking issue for release notes of #148052: Stabilize `const_mul_add` | This issue tracks the release notes text for #148052. cc @tgross35, @Mark-Simulacrum -- 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#p | labels: T-lang, relnotes, relnotes-tracking-issue"}
+{"id": "rust_150532", "text": "Hang in trait solver with mutually recursive trait 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 trait MyTrait<T> {} struct Foo; struct Bar; impl<T> MyTrait<T> for Foo wher | labels: T-compiler, C-bug, I-hang, fixed-by-next-solver"}
+{"id": "rust_149674", "text": "Tracking issue for release notes of #147224: Emscripten: Turn wasm-eh on by default | This issue tracks the release notes text for #147224. cc @hoodmane, @bjorn3 -- 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#preparing- | labels: T-compiler, relnotes, relnotes-tracking-issue"}
+{"id": "rust_148874", "text": "Tracking issue for release notes of #148798: `OsString` `Debug` implementation prints escaped single quotes | This issue tracks the release notes text for #148798. cc @tamird, @tamird -- 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#preparing-re | labels: relnotes, T-libs, A-fmt, relnotes-tracking-issue"}
+{"id": "rust_148824", "text": "Tracking issue for release notes of #65816: Tracking issue for `vec_into_raw_parts` | This issue tracks the release notes text for #65816. cc @shepmaster -- 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#preparing-release- | labels: A-collections, T-libs-api, relnotes, A-raw-pointers, relnotes-tracking-issue"}
+{"id": "rust_148582", "text": "Tracking issue for release notes of #133508: Tracking Issue for `core_slice_as_array`. | This issue tracks the release notes text for #133508. cc @bjoernager -- 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#preparing-release | labels: T-libs-api, relnotes, relnotes-tracking-issue"}
+{"id": "rust_148419", "text": "Tracking issue for release notes of #146978: Emit error when using path-segment keyword as cfg pred | This issue tracks the release notes text for #146978. cc @mu001999, @petrochenkov -- 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#prep | labels: A-attributes, T-lang, T-compiler, relnotes, relnotes-tracking-issue"}
+{"id": "rust_148304", "text": "Tracking issue for release notes of #148301: [rustdoc search] Include extern crates when filtering on `import` | This issue tracks the release notes text for #148301. cc @GuillaumeGomez, @notriddle -- 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#p | labels: T-rustdoc, relnotes, A-rustdoc-search, T-rustdoc-frontend, relnotes-tracking-issue"}
+{"id": "rust_148145", "text": "Tracking issue for release notes of #145974: Stabilize -Zno-jump-tables into -Cjump-tables=bool | This issue tracks the release notes text for #145974. cc @pmur, @jieyouxu -- 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#preparing-re | labels: A-LLVM, T-compiler, relnotes, relnotes-tracking-issue"}
+{"id": "rust_148258", "text": "Tracking issue for release notes of #148176: [rustdoc] Include attribute and derive macros when filtering on \"macros\" | This issue tracks the release notes text for #148176. cc @GuillaumeGomez, @notriddle -- 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#p | labels: T-rustdoc, relnotes, A-rustdoc-search, T-rustdoc-frontend, relnotes-tracking-issue"}
+{"id": "rust_148111", "text": "Tracking issue for release notes of #145665: Don't require `T: RefUnwindSafe` for `vec::IntoIter<T>: UnwindSafe` | This issue tracks the release notes text for #145665. cc @GrigorenkoPV, @the8472 -- 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#prepa | labels: T-libs-api, relnotes, relnotes-tracking-issue"}
+{"id": "rust_148107", "text": "Tracking issue for release notes of #135889: Tracking Issue for `VecDeque::pop_front_if` & `VecDeque::pop_back_if` | This issue tracks the release notes text for #135889. cc @GrigorenkoPV -- 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#preparing-relea | labels: T-libs-api, relnotes, relnotes-tracking-issue"}
+{"id": "rust_148109", "text": "Tracking issue for release notes of #146705: Tracking Issue for `fmt_from_fn` | This issue tracks the release notes text for #146705. cc @jmillikin -- 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#preparing-release- | labels: T-libs-api, relnotes, relnotes-tracking-issue"}
+{"id": "rust_151799", "text": "Request to Participate and Share Academic Survey on Code Review in OSS Security | Hello, I hope you are doing well. My name is Md Niaz Morshed ([[mmorshed@crimson.ua.edu](mailto:mmorshed@crimson.ua.edu)]), and I am a PhD candidate at the University of Alabama conducting an academic survey titled “Understanding Information Needs When Looking | labels: C-discussion"}
+{"id": "rust_151843", "text": "Rust Compiler Reads Code After return | I rarely come here, but I’ll just write this because, in my opinion, it’s a language bug. The problem is very simple: ```Rust fn demo() -> () { return; 5 + 2; // ⚠ warning: unreachable code some_undefined_var; // ❌ error: cannot find value `some_undefined_var` | labels: A-diagnostics, T-compiler, C-discussion"}
+{"id": "rust_142602", "text": "E0308 doesn't provide a help message in loops when using `let-else` | ### Code ```Rust pub fn main() { let a = loop { if true { break; } let Some(_) = Some(5) else { break 3; }; }; } ``` ### Current output ```Shell error[E0308]: mismatched types --> src/lib.rs:7:19 | 7 | break 3; | ^ expected `()`, found integer For more informa | labels: A-diagnostics, T-compiler, D-terse, F-let_else"}
+{"id": "rust_151826", "text": "Partial architecture mismatch: X86_64 objects found in precompiled libcompiler_builtins for loongarch64-unknown-none | <!-- 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 am cross-compiling a kernel project from an **x86_64 Linux host** to the **loongarch64-unknown-none* | labels: C-bug, O-loongarch"}
+{"id": "rust_151797", "text": "Lifetime hygiene comments missing `#N` suffix in `-Zunpretty=expanded,hygiene` output | <!-- 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 the following code (based on [this test file](https://github.com/zalanlevai/mutest-rs/blob/515 | labels: A-pretty, T-compiler, C-bug, A-hygiene"}
+{"id": "rust_143256", "text": "false positive `unused_parens` causes syntax error around labled loops with ifs | Using the following flags `--force-warn unused_parens` this code: ```rust fn foo() { let _x = || 'outer: loop { let inner = 'inner: loop { let i = Default::default(); if (break 'outer i) { loop { break 'inner 5i8; }; } else if true { break 'inner 6; } break 7; | labels: T-compiler, C-bug, A-suggestion-diagnostics, D-invalid-suggestion, L-unused_parens"}
+{"id": "rust_151672", "text": "Issue | <!-- 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 <command> ``` ##"}
+{"id": "rust_151801", "text": "Issue | <!-- 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 <command> ``` ##"}
+{"id": "rust_89106", "text": "{f32,f64}::DIGITS is misleading | While they come with a caveat that they are an \"approximate\" value, these constants are treated as gospel and [invoked by clippy in the excessive_precision lint to create a warning](https://github.com/rust-lang/rust-clippy/blob/92ca25b3ec8cef291f1d3b37bfd01d3c | labels: A-docs, A-floating-point"}
+{"id": "rust_136420", "text": "Rust fails to coerce to a fn pointer when passing an array as an argument to a generic function. | I tried this code: ```rust fn foo() {} fn bar() {} fn main() { let _a = if true { foo } else { bar }; let _b = vec![foo, bar]; let _c = [foo, bar]; d(if true { foo } else { bar }); e(vec![foo, bar]); f([foo, bar]); } fn d<T>(_: T) {} fn e<T>(_: Vec<T>) {} fn f | labels: T-compiler, A-inference, C-bug, A-coercions, T-types"}
+{"id": "rust_116237", "text": "Scoped thread implicit join doesn't wait for thread locals to be dropped | See also https://github.com/rust-lang/rust/issues/116179: > When a scoped thread is **_implicitly_** joined, the destructors of thread-local variables are not guaranteed to have completed when the scope is exited. When a scoped thread is **_explicitly_** joine | labels: T-libs-api, A-thread-locals, C-bug, finished-final-comment-period, disposition-close, A-thread"}
+{"id": "rust_127571", "text": "Guarantee that thread-local storage destructors run before join() returns | As discussed in https://github.com/rust-lang/rust/issues/116237#issuecomment-2217941740, this is already the implemented behaviour but it is not guaranteed. Unless there is a good reason not to, this guarantee should be made and documented. | labels: T-libs-api, A-docs, A-thread-locals, C-discussion, A-thread"}
+{"id": "rust_151269", "text": "`unused_must_use` inside macro suggests `let _ = ` on the macro invocation | ### Code ```Rust fn error() -> Result<(), ()> { Err(()) // actual value irrelevant } macro_rules! foo { () => { { error(); } } } fn main() { let _ = foo!(); } ``` ### Current output ```Shell warning: unused `Result` that must be used --> src/main.rs:15:13 | 14 | labels: A-diagnostics, T-compiler"}
+{"id": "rust_64458", "text": "Foreign type tests not covering all operations | For example foreign type pointer comparison is not tested. Also `&(*val).0` where field `0` of `*val` is a foreign type is not tested. As a last thing pointer to `*mut ForeignType` casting it not tested. These were all cases which were mishandled in [rustc_cod | labels: A-testsuite, C-enhancement, A-FFI, E-needs-test, T-compiler, requires-nightly"}
+{"id": "rust_114430", "text": "Tweak output of E0599 to make it less verbose | ### Code ```Rust struct Foo; trait Bar {} trait Baz {} trait Bat { fn bat(&self); } impl<T> Bat for T where T: 'static + Bar + Baz { fn bat(&self) { println!(\"generic bat\"); } } pub fn main() { Foo::bat(()); } ``` ### Current output ```Shell error[E0599]: the  | labels: A-diagnostics, P-low, T-compiler, D-papercut, D-verbose"}
+{"id": "rust_151422", "text": "Rustdoc fails contrast check for a certain element. | <!-- Thank you for filing a rustdoc issue! Rustdoc is the tool that handles the generation of docs. It is usually invoked via `cargo doc`, but can also be used directly. If you have an issue with the actual content of the docs, use the \"Documentation problem\"  | labels: E-easy, T-rustdoc, C-bug, A-rustdoc-ui, T-rustdoc-frontend, A-a11y"}
+{"id": "rust_150399", "text": "Add comment when new directory is added to `tests/ui` | If a new directory is added under [tests/ui](https://github.com/rust-lang/rust/tree/main/tests/ui), it would be nice to add a comment to [tests/ui/README.md](https://github.com/rust-lang/rust/blob/main/tests/ui/README.md) to update it as well. There are a few  | labels: A-testsuite, T-compiler"}
+{"id": "rust_150174", "text": "E0507: `AsyncFn` vs `AsyncFnOnce` not given as cause of error, unlike `Fn` vs `FnOnce` | Contrived example (that might be possible to distill further, but it's short enough and gets the job done): ```rust pub async fn in_transaction<F>(callback: F) -> Result<(), ()> where F: AsyncFn() -> Result<(), ()>, { let result = callback().await?; Ok(result) | labels: A-diagnostics, T-compiler, C-bug, A-async-closures, D-lack-of-suggestion"}
+{"id": "rust_151595", "text": "[ICE]: rustc panicked at compiler\\rustc_mir_build\\src\\builder\\matches\\mod.rs:2176:44 | <!-- 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, A-closures, T-lang, T-compiler, regression-from-stable-to-beta, A-impl-trait"}
+{"id": "rust_146515", "text": "incorrect \"consider annotating `ContainsRc<T>` with `#[derive(Clone)]`\" | ```rust use std::rc::Rc; #[derive(Clone)] struct ContainsRc<T> { value: Rc<T>, } fn clone_me<T>(x: &ContainsRc<T>) -> ContainsRc<T> { x.clone() } ``` results in ```rust error[E0308]: mismatched types --> src/lib.rs:9:5 | 8 | fn clone_me<T>(x: &ContainsRc<T>) - | labels: A-diagnostics, T-compiler, A-suggestion-diagnostics, D-invalid-suggestion"}
+{"id": "rust_151548", "text": "Symbol of items instantiated w/ dyn trait w/ assoc const bindings not demangled (aka `backtrace`'s `rustc-demangle` needs to be bumped) | #### Reproducer ```rs #![feature(min_generic_const_args)] trait Trait { #[type_const] const N: usize; } fn f<T: ?Sized>() { panic!(); } fn main() { f::<dyn Trait<N = 1>>(); } ``` #### Program Output ``` thread 'main' (13) panicked at src/main.rs:5:21: explicit | labels: C-bug, T-libs, A-dyn-trait, A-backtrace, F-min_generic_const_args, A-name-mangling"}
+{"id": "rust_79878", "text": "Document impl block visibility | It seems that if the type is visible, an impl's pub methods can be used, even if such an impl is encased in multiple private modules. https://play.rust-lang.org/?version=nightly&mode=debug&edition=2015&gist=bf21f358b4b57075d1243a3b07d93da9 I cannot find anywhe | labels: C-enhancement, A-visibility, T-lang, A-docs"}
+{"id": "rust_151636", "text": "Next solver hangs on cyclic associated type projection in blanket implementation 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 trait StreamingIterator { type Item<'a> ; } struct StreamEnumerate<I> { ite | labels: A-trait-system, C-bug, I-hang, T-types, WG-trait-system-refactor"}
+{"id": "rust_151238", "text": "ICE: `parse_expected_identifier_found_keyword_str` | see #149692 for prev case <!-- \u001b[31mICE\u001b[0m: Rustc ./6A037843FEA62B4ED74383176913966D09BD78A595E9BE80AB8E96392DBAAC1A.rs '--edition=2024 -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_parse/src/parser/diagnostics.rs:2267:44: | labels: A-diagnostics, I-ICE, A-parser, T-compiler, C-bug"}
+{"id": "rust_117242", "text": "Add `core` and `alloc` columns to platform support | It would be nice instead of asterisks and double asterisks, that `core` and `alloc` had their own column, I think this would make it much easier for people skim through the table for compatibility without having to look up what the asterisks' mean. | labels: C-enhancement, A-docs"}
+{"id": "rust_137407", "text": "Bad codegen for widen followed by ARM `vdupq_n_*` | <!-- Thank you for filing a regression report! 🐛 A regression is something that changed between versions of Rust but was not supposed to. Please provide a short summary of the regression, along with any information you feel is relevant to replicate it. --> ### | labels: P-medium, T-compiler, regression-from-stable-to-stable, A-SIMD, O-AArch64, C-optimization"}
+{"id": "rust_60637", "text": "Inlining + target_feature broken in powerpc64 | [godbolt](https://godbolt.org/z/FsNj8l) ```rust #![feature(repr_simd, powerpc_target_feature)] #![allow(non_camel_case_types)] #[repr(simd)] pub struct u32x4(u32, u32, u32, u32); impl u32x4 { #[inline] // #[inline(always)] fn splat(x: u32) -> Self { u32x4(x, x | labels: A-LLVM, T-compiler, O-PowerPC, A-SIMD, C-bug"}
+{"id": "rust_150464", "text": "regression: \"cycle detected when borrow-checking\" in `offset_of!` | ``` [INFO] [stdout] error[E0391]: cycle detected when borrow-checking `firmware::operation::implement::stm::gain::tests::test_phase_half` [INFO] [stdout] --> src/firmware/operation/implement/stm/gain.rs:649:5 [INFO] [stdout] | [INFO] [stdout] 649 | fn test_pha | labels: P-medium, T-lang, T-compiler, regression-from-stable-to-beta, regression-from-stable-to-stable, C-bug"}
+{"id": "rust_151730", "text": "[ICE]: builtin derive created an unaligned reference | <!-- 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"}
+{"id": "rust_145580", "text": "Found unstable fingerprints for associated_items(foo[c46e]::{impl#0}) | ### Code ```shell git clone https://github.com/rust-lang/rustc_codegen_cranelift cg_clif cd cg_clif git checkout 420235c0f87bd379e3bd318b401ebbf08d82c44d # incr_ice_repro branch ./scripts/test_rustc_tests.sh ``` ### Meta `rustc --version --verbose`: ``` rustc  | labels: I-ICE, T-compiler, A-incr-comp, C-bug, E-needs-mcve"}
+{"id": "rust_151226", "text": "ICE `Unable to verify registry association` / `!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"}
+{"id": "rust_150091", "text": "ICE: inference variables in normalized parameter environment: unconstrained type | <!-- 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"}
+{"id": "rust_92738", "text": "\"unknown file type lib.rmeta\" when compiling Emscripten side module | Because of the `lib.rmeta` file, linking rust libraries doesn't work with `-Wl,--whole-archive`. When compiling an Emscripten side module as follows: ```sh export RUSTFLAGS=\"-C link-arg=-s -C link-arg=SIDE_MODULE=1 -C relocation-model=pic -C target-feature=+mu | labels: A-linkage, O-wasm, C-bug, O-emscripten"}
+{"id": "rust_110317", "text": "std::process:Command::spawn panics when pre_exec hook fails if SIGCHLD is ignored | On Linux when a `CommandExt::pre_exec` hook is in use, `std::process::Command::spawn` forks, calls `do_exec` and then runs each of the hooks in order. If `do_exec` fails (if a pre_exec hook or exec itself fails for example), the `Err` bubbles up and the child  | labels: C-bug, T-libs, A-io, O-unix, A-process"}
+{"id": "rust_151673", "text": "\"tuple constructor with invalid base path\" bug or confusing diagnostic - min_generic_const_args | I tried this code with `nightly` feature `min_generic_const_args` #132980: ```rust #![allow(incomplete_features)] #![feature(min_generic_const_args)] pub trait NonDropChecker : Sized { #[type_const] const ND: usize; } impl<T> NonDropChecker for T { #[type_cons | labels: A-diagnostics, T-compiler, D-confusing, F-min_generic_const_args"}
+{"id": "rust_65868", "text": "Slightly confusing grammar in pinning docs. | Hi, I've just read the `std::pin` docs as part of learning `std::future::Future` and attempting to write my own combinator. This section is pretty dense for my first read, and only at the very end, when it mentioned `Future` combinators did I realize I had a m | labels: C-enhancement, T-libs-api, A-docs"}

validation_labeled.jsonl

@@ -0,0 +1,100 @@
+{"id": "rust_152231", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_152470", "text": "[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", "label": "low", "label_id": 3}
+{"id": "rust_150899", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_104463", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_152510", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_147465", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_145866", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_128203", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_147370", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_148372", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_151807", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_148738", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_71043", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_143531", "text": "`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", "label": "medium", "label_id": 2}
+{"id": "rust_151832", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_71850", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_49569", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152347", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151124", "text": "ICE: `DefId(..)): reachable Public > nominal Restricted(DefId(..)` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_152004", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_151791", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152482", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_74756", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_151904", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_147883", "text": "\"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", "label": "high", "label_id": 1}
+{"id": "rust_115399", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_122620", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_141679", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_81059", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_82775", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_151705", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_151818", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151926", "text": "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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152255", "text": "\"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", "label": "critical_bug", "label_id": 0}
+{"id": "rust_124309", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_88051", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152468", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_152467", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_151358", "text": "[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", "label": "high", "label_id": 1}
+{"id": "rust_152464", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_152453", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_142778", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_141540", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_111164", "text": "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", "label": "low", "label_id": 3}
+{"id": "rust_109829", "text": "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", "label": "question", "label_id": 4}
+{"id": "rust_143358", "text": "ICE: `unhandled node ConstArg(ConstArg ` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_131292", "text": "ICE: `bpos.to_u32() >= mbc.pos.to_u32() + mbc.bytes as u32` | <!-- \u001b[31mICE\u001b[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", "label": "high", "label_id": 1}
+{"id": "rust_152376", "text": "`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", "label": "question", "label_id": 4}
+{"id": "rust_151273", "text": "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", "label": "high", "label_id": 1}
+{"id": "rust_80317", "text": "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", "label": "medium", "label_id": 2}
+{"id": "rust_138274", "text": "[bug] When I Use tauri-plugin-http and reqwest either, I got a 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, P-medium, T-compiler, regression-from-stable-to-stable, C-bug, A-coercions", "label": "critical_bug", "label_id": 0}
+{"id": "rust_137916", "text": "ICE Unsize coercion, but `Box<{async block@file.rs}>` isn't coercible to `Box<dyn Send>` | <!-- 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, E-mentor, T-compiler, E-medium, C-bug, S-has-mcve", "label": "high", "label_id": 1}
+{"id": "rust_151323", "text": "[ICE]: !tcx.next_trait_solver_globally() | <!-- \u001b[31mICE\u001b[0m: Rustc ./2969A4590773DF5416935FBB7FE10D4070C5F412CB47CD0E21F34E735F4A479B.rs '--edition=2024 -Znext-solver=globally -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' ($TID) panicked at compiler/rustc_hir_analysis/src/collect/type_of/opaque.rs: | labels: I-ICE, T-compiler, C-bug, WG-trait-system-refactor", "label": "high", "label_id": 1}
+{"id": "rust_142931", "text": "normalize_lexically should mention other functions that do basic normalization | ### Location https://doc.rust-lang.org/nightly/std/path/struct.Path.html#method.normalize_lexically ### Summary both the PartialEq impl for Path and Path::components will normalize away non-leading `.` and duplicate/trailing slashes. This is \"good enough\" for  | labels: A-docs, T-libs", "label": "low", "label_id": 3}
+{"id": "rust_151322", "text": "[ICE]: !self.tcx.next_trait_solver_globally() | <!-- 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-type_alias_impl_trait, WG-trait-system-refactor", "label": "high", "label_id": 1}
+{"id": "rust_145989", "text": "std::pointer::Nonnull should guarantee ABI compatibility for non-null pointer values | Can we rely on `NonNull<T>` having the same representation as `*mut T` for all non-null values of that type? In particular, can we rely on e.g. `NonNull<std::ffi::c_void>` being ABI compatible with C `void*` for non-null pointers? It seems pretty likely that t | labels: T-libs-api, A-raw-pointers, C-discussion, T-opsem", "label": "question", "label_id": 4}
+{"id": "rust_144060", "text": "Lint regression: `dead_code` ignores `#[allow(dead_code)]` on traits | ### Code ```rust #[allow(dead_code)] trait Foo { const FOO: u32; } impl Foo for u32 { const FOO: u32 = roundtrip(0); } const fn roundtrip(x: u32) -> u32 { x } ``` https://play.rust-lang.org/?version=nightly&mode=debug&edition=2024&gist=1991c4121122ea00f92d7386 | labels: A-diagnostics, P-low, T-compiler, regression-from-stable-to-stable, L-false-positive, I-lang-radar", "label": "critical_bug", "label_id": 0}
+{"id": "rust_151026", "text": "stable compiler should provide better advice for `Step` trait failures | ### Code ```Rust fn custom_range() { struct Foo(u32); let x = Foo(0); let y = Foo(10); for value in x..y {} } ``` ### Current output ```Shell error[E0277]: the trait bound `Foo: Step` is not satisfied --> src/lib.rs:7:18 | 7 | for value in x..y {} | ^^^^ unsat | labels: A-diagnostics, T-compiler", "label": "question", "label_id": 4}
+{"id": "rust_82171", "text": "Unclear compiler error when `impl Trait` return value captures non-'static argument | (cc @estebank) I tried this code (the explicit `'static` lifetime is unnecessary but emphasizes the implicit `'static` requirement of `impl Trait`): ```rust fn foo<T>(a: T) -> impl Iterator<Item = String> + 'static where T: std::fmt::Display { std::iter::once( | labels: A-diagnostics, A-lifetimes, T-compiler, A-impl-trait, C-bug, D-papercut", "label": "medium", "label_id": 2}
+{"id": "rust_152262", "text": "`-Clinker-plugin-lto` is required for inlining stdlib with LTO | ## Experiment setup Considering the following code: ```rust #![no_main] extern \"C\" { fn ftn() -> u32; } #[unsafe(export_name = \"_start\")] fn _start() -> f64 { let f77 = unsafe { ftn() } as f64; f64::cbrt(f77) } ``` The code is incorrect but quite good for demo | labels: A-linkage, T-compiler, C-bug, A-LTO", "label": "medium", "label_id": 2}
+{"id": "rust_152360", "text": "Issue | <!-- 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", "label": "question", "label_id": 4}
+{"id": "rust_151524", "text": "Missed optimization: introducing a temporary ownership move of `Vec` changes optimized code generation in `main`. | <!-- 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://godbolt.org/z/Ts7ss7zj4 ```rust #[no_mangle] fn grow(v: &mut Vec<isize>) {  | labels: C-optimization", "label": "medium", "label_id": 2}
+{"id": "rust_142577", "text": "Tracking Issue for reflection | This is a tracking issue for an un-RFC-ed language feature experiment The feature gate for the issue is `#![feature(reflection)]`. ### About tracking issues Tracking issues are used to record the overall progress of implementation. They are also used as hubs c | labels: T-lang, T-compiler, C-tracking-issue, S-tracking-unimplemented, B-experimental", "label": "question", "label_id": 4}
+{"id": "rust_149954", "text": "ICE: `None.unwrap()` in `tokenstream.rs` during `resolver_for_lowering_raw` | This bug was found with a fuzzer ([tree-splicer](https://github.com/langston-barrett/tree-splicer)). Reduced with [treereduce](https://github.com/langston-barrett/treereduce), then hand-reduced. [playground](https://play.rust-lang.org/?version=nightly&mode=deb | labels: I-ICE, A-parser, A-macros, T-compiler, C-bug", "label": "high", "label_id": 1}
+{"id": "rust_152374", "text": "False postive: warning of unnecessary `unsafe` block | ### Code I tried this code: ```rust fn main() { let a = unsafe { core::arch::x86_64::__cpuid_count(0, 0) }; dbg!(a); } ``` I expected to see this happen: it compiles without warnings. Instead, this happened: it compiles with a warning of unnecessary `unsafe` b | labels: T-lang, T-libs-api, C-discussion, S-has-bisection", "label": "question", "label_id": 4}
+{"id": "rust_97804", "text": "Array Repeat operator should not use a loop for small sizes | This likely caused poor assembly for `Simd::splat` in some circumstances: https://rust-lang.zulipchat.com/#narrow/stream/257879-project-portable-simd/topic/Very.20bad.20.60u16x8.3A.3Asplat.60.20codegen.20on.20x86_64 I opened a PR for a workaround: https://gith | labels: A-LLVM, I-slow, A-codegen, E-needs-test, T-compiler, A-SIMD", "label": "medium", "label_id": 2}
+{"id": "rust_55713", "text": "multiline cfg_attr in a doctest outputs a corrupted snippet | With following doctest, where the cfg attribute spans multiple lines, the final program is invalid: the wrapping `main` method doesn't take into account the dangling `stdsimd))]` line that closes the attribute. ```rust /// ```rust /// # #![cfg_attr(not(dox), f | labels: T-rustdoc, A-doctests", "label": "medium", "label_id": 2}
+{"id": "rust_114768", "text": "ICE: Failed to extract DefId: opt_local_def_id_to_hir_id | ### Code Can be reproduced by first building (in debug mode) `crates/yaboc-hir` of https://github.com/8051enthusiast/yabo at commit `442536c09df2fe898bfeda81a2788bf9dce9dc19` after a `cargo clean` and then building at commit `5d5d795041d55d3bcbe21c5052807711dd | labels: I-ICE, T-compiler, A-incr-comp, C-bug, S-has-mcve", "label": "high", "label_id": 1}
+{"id": "rust_152331", "text": "[ICE]: `arg len already exists` | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '' 'thread 'rustc' ($TID) panicked at compiler/rustc_errors/src/diagnostic.rs:359:9: 'arg len already exists'', 'thread 'rustc' ($TID) panicked at compiler/rustc_errors/src/diagnostic.rs:359:9: 'arg len already exists'' File: /t | labels: I-ICE, T-compiler, C-bug, requires-debug-assertions", "label": "high", "label_id": 1}
+{"id": "rust_149568", "text": "Method `SourceFile::normalized_byte_pos` is broken | I have been looking through the source of `rustc_span` and stumbled upon an inconsistent usage of byte positions. The problematic code is from [SourceFile::normalized_byte_pos](https://github.com/rust-lang/rust/blob/646a3f8c15baefb98dc6e0c1c1ba3356db702d2a/com | labels: T-compiler, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_152158", "text": "ICE due to RBV not handling RTN where trait is behind trait alias | Context: It's HIR ty lowering's job to resolve+lower RTN. However, it needs the lifetime resolutions from RBV which runs before HIR ty lowering and which (unfortunately) sort of duplicates some of HIR ty lowering code to resolve RTN itself. Now, while HIR ty l | labels: A-lifetimes, I-ICE, T-compiler, C-bug, F-trait_alias, S-has-mcve", "label": "high", "label_id": 1}
+{"id": "rust_152244", "text": "ICEs (in debug mode) due to RBV not expanding trait aliases when collecting bound vars from supertrait bounds | 1st reproducer: ```rs #![feature(trait_alias)] trait A<'a> { type X; } trait B: for<'a> A<'a> {} trait C = B; fn f<T>() where T: C<X: Copy> {} ``` Compiler panic message w/o backtrace: ``` thread 'rustc' (47550) panicked at compiler/rustc_type_ir/src/binder.rs | labels: I-ICE, T-compiler, C-bug, F-trait_alias, S-has-mcve, T-types", "label": "high", "label_id": 1}
+{"id": "rust_133101", "text": "Add mention that `ilog2` and `checked_ilog2` can be used to get the number of bits in an integer | ### Location - [`{integer}::ilog2`](https://doc.rust-lang.org/nightly/core/primitive.i32.html#method.ilog2) - [`{integer}::checked_ilog2`](https://doc.rust-lang.org/nightly/core/primitive.i32.html#method.checked_ilog2) - [`NonZero::ilog2`](https://doc.rust-lan | labels: A-docs, T-libs", "label": "question", "label_id": 4}
+{"id": "rust_152348", "text": "regression: parameter may not live long enough | ``` [INFO] [stdout] error[E0310]: the parameter type `T` may not live long enough [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/cogo-0.1.2/src/yield_now.rs:35:13 [INFO] [stdout] | [INFO] [stdout] 35 | let r = resour | labels: regression-from-stable-to-beta, I-prioritize", "label": "critical_bug", "label_id": 0}
+{"id": "rust_71025", "text": "Sub-optimal codegen: Unnecessarily dumping AVX registers to stack | <!-- 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 ([example 1](https://rust.godbolt.org/z/86FfSi)), in which we have a public function | labels: I-slow, C-enhancement, A-codegen, T-compiler, A-SIMD, C-optimization", "label": "low", "label_id": 3}
+{"id": "rust_152024", "text": "`unused_mut` false positive due to borrow-checking error | ### Code ```Rust struct Thing; impl Drop for Thing { fn drop(&mut self) {} } fn main() { let mut t; let mut b = None; loop { t = Thing; b.insert(&t); } } ``` ### Current output ```Shell warning: variable does not need to be mutable --> src/main.rs:7:9 | 7 | le | labels: A-lints, A-diagnostics, A-destructors, A-borrow-checker, T-compiler, L-unused_mut", "label": "medium", "label_id": 2}
+{"id": "rust_150352", "text": "Conflict markers with nonstandard lengths are not recognized as such | ### Code ```Rust <<<<<<<< ======== >>>>>>>> fn main() {} ``` ### Current output ```Shell error: expected identifier, found `<<` --> test.rs:1:1 | 1 | <<<<<<<< | ^^ expected identifier error: aborting due to 1 previous error ``` ### Desired output ```Shell erro | labels: A-diagnostics, T-compiler", "label": "low", "label_id": 3}
+{"id": "rust_141313", "text": "GVN misunderstands aliasing, can create overlapping assignments (again) | This looks very similar to https://github.com/rust-lang/rust/issues/141038, but the compiler that found this has the patch that was linked to that issue. Reduced example from rustlantis, which is accepted by Miri without optimizations enabled: ```rust #![featu | labels: P-high, T-compiler, I-unsound, C-bug, A-mir-opt, I-miscompile", "label": "high", "label_id": 1}
+{"id": "rust_127215", "text": "`*x == *y` for trait objects produce move error, so it is not equivalent to `PartialEq::eq(&*x, &*y)` even though the reference says it is | [The following code produces a move error](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=45b377544d27adffcaa1f0b38cbe22e0): ```rust trait Animal { fn noise(&self) -> String; } impl PartialEq for dyn Animal { fn eq(&self, other: &Self | labels: A-diagnostics, A-borrow-checker, T-compiler, A-docs, C-bug, A-dyn-trait", "label": "low", "label_id": 3}
+{"id": "rust_150553", "text": "`#[expect(redundant_lifetimes)]` doesn't work when `#[derive(Debug)]` is present | Consider the following code: ```rust #![deny(redundant_lifetimes)] use std::fmt::Debug; #[derive(Debug)] pub struct RefWrapper<'a, T> where 'a: 'static, T: Debug, { pub t_ref: &'a T } ``` As expected, the compiler throws an error because the `'a` lifetime is r | labels: T-lang, C-bug, I-lang-radar", "label": "medium", "label_id": 2}
+{"id": "rust_135894", "text": "Tracking Issue for `atomic_try_update` | Feature gate: `#![feature(atomic_try_update)]` This is a tracking issue for an infallible version of `AtomicT::fetch_update` as well as a new name for the existing fallible version. When and if this gets stabilized, the existing `fetch_update` should be marked | labels: T-libs-api, C-tracking-issue, disposition-merge, finished-final-comment-period", "label": "question", "label_id": 4}
+{"id": "rust_138910", "text": "Linker-plugin-based LTO with -flto in clang not working | The original issue title was \"Implement cross-language ThinLTO,\" #49879 but when it was stabilized, the PR title became \"Stabilize linker-plugin based LTO (aka cross-language LTO),\" #58057 which seems to imply that fullLTO is available. The Rustc book states,  | labels: A-LLVM, T-compiler, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_151966", "text": "LLDB testing should be disabled | Per @khyperia in https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/debuginfo.20tests.20broken.20locally/with/571307617 these tests don't run in CI. On a contributor's machine they can easily fail to pass, for reasons I am not going | labels: A-testsuite, A-debuginfo, T-compiler, C-bug", "label": "low", "label_id": 3}
+{"id": "rust_136873", "text": "Tracking Issue for `cold_path` | Feature gate: `#![feature(cold_path)]` This is a tracking issue for `core::hint::{cold_path}`. Please also see the meta discussion at https://github.com/rust-lang/rust/issues/26179. `#![feature(likely_unlikely)]` was split to a new tracking issue: https://gith | labels: T-lang, T-libs-api, C-tracking-issue", "label": "question", "label_id": 4}
+{"id": "rust_26179", "text": "Meta tracking issue for branch hints (RFC 1131) | Tracking and meta discussion for branch and path hinting, including: - `likely`/`unlikely` as accepted in rust-lang/rfcs#1131 (much has changed since this RFC) - `core::hint::{likely, unlikely}` https://github.com/rust-lang/rust/issues/151619 - `core::hint::co | labels: metabug, B-RFC-approved, T-lang, B-unstable, E-help-wanted, C-tracking-issue", "label": "question", "label_id": 4}
+{"id": "rust_127031", "text": "`hir::Body`'s documentation incorrectly suggests it doesn't contain parmaeter info for closures | ### Location https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/hir/struct.Body.html ### Summary Noticed this in rust-lang/rust-clippy#12981. The documentation says \"a function\" which I assume was meant to imply both a function/method call and closure w | labels: T-compiler, A-docs", "label": "low", "label_id": 3}
+{"id": "rust_151496", "text": "Local `rustc-docs` could make use of local pages for `std` types | Posting this for @blyxyas and big thanks for having spotted this issue real quick :) ### Location (URL) The same problem persists in many different pages, just to pick an example on my machine: `$RUSTUP_HOME/toolchains/nightly-aarch64-apple-darwin/share/doc/ru | labels: T-rustdoc, A-docs", "label": "low", "label_id": 3}
+{"id": "rust_152161", "text": "Inconsistent borrow-checking and temporary lifetime behavior with async closures | I've discovered some rather strange behavior involving borrow-checking and/or temporary lifetimes of async closures. Why does it behave this way? In the snippets below, `black_box` calls are done to be really clear that const promotion isn't occurring. The fol | labels: A-borrow-checker, C-bug, A-async-closures", "label": "medium", "label_id": 2}
+{"id": "rust_152123", "text": "mGCA: Support directly represented negated literals | Follow up of #150618 and #150699. We currently support directly represented literals as a `hir::ConstArgKind::Literal` but we don't support negated literals as such a representation: ```rust #![feature(adt_const_params, min_generic_const_args)] use std::marker | labels: E-easy, E-mentor, T-compiler, A-const-generics, F-adt_const_params, T-types", "label": "question", "label_id": 4}
+{"id": "rust_138226", "text": "ICE：expected const for `N/#0` (N/#0/0) but found Type(A<N/#0>) when instantiating args=[A<N/#0>] | <!-- 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-inherent_associated_types, S-bug-has-test, requires-debug-assertions", "label": "high", "label_id": 1}
+{"id": "rust_150960", "text": "ICE: index out of bounds: the len is 0 but the index is 0 | Here is the example code that I found: ```rust #![allow(incomplete_features)] #![feature(min_generic_const_args)] pub struct A; impl A { #[type_const] const LEN: usize = 4; #[allow(unused_braces)] fn arr() -> [u8; const { Self::LEN }] { return [0u8; const { Se | labels: I-ICE, T-compiler, C-bug, S-bug-has-test, F-associated_const_equality, F-min_generic_const_args", "label": "question", "label_id": 4}
+{"id": "rust_138089", "text": "ICE: expected region but found Type | <!-- \u001b[31mICE\u001b[0m: Rustc ./a.rs '-Zcrate-attr=feature(generic_const_exprs) -Zcrate-attr=feature(min_generic_const_args) -Zcrate-attr=feature(inherent_associated_types) -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' panicked at /rustc/30f168ef811aec63124eac67 | labels: I-ICE, T-compiler, C-bug, F-generic_const_exprs, F-inherent_associated_types, S-bug-has-test", "label": "high", "label_id": 1}
+{"id": "rust_151027", "text": "ICE: `expected type for param #0 in [N/#0]` | <!-- 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-min_generic_const_args", "label": "high", "label_id": 1}
+{"id": "rust_151865", "text": "1.94 beta regression: \"malformed `doc` attribute input\" | The following errors are all the errors found in the 1.94 beta crater run that are related to the `doc` attribute. ## Error 1 ``` [INFO] [stdout] error[E0538]: malformed `doc` attribute input [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crat | labels: A-attributes, P-high, T-lang, T-compiler, regression-from-stable-to-beta, C-bug", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152124", "text": "mGCA: consolidate type const checks on `tcx.is_type_const` | Under `feature(min_generic_const_args)` const items have been split into two, \"const items\" and \"type const items\". Type const items are written with the `#[type_const]` attribute applied to the syntax of a normal const item. In some places in the compiler we  | labels: E-easy, C-cleanup, E-mentor, T-compiler, A-const-generics, T-types", "label": "low", "label_id": 3}
+{"id": "rust_151967", "text": "Unexpected result from recursive macro rule | <!-- 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 macro_rules! text_token { (\"{%\", $($token: literal,)*) => { println!(\"Found | labels: A-macros, C-bug, C-discussion, T-rust-analyzer", "label": "question", "label_id": 4}
+{"id": "rust_151950", "text": "unmangled symbols are not escaped in naked/global assembly | I tried this code: ```rust unsafe extern \"C\" { #[link_name = \"memset]; mov eax, 1; #\"] unsafe fn inject(); } #[unsafe(export_name = \"memset]; mov eax, 1; #\")] extern \"C\" fn inject_() {} #[unsafe(naked)] extern \"C\" fn print_0() -> usize { core::arch::naked_asm! | labels: A-codegen, C-bug", "label": "medium", "label_id": 2}
+{"id": "rust_108894", "text": "#[derive(Clone, Copy)] doesn't work | I tried this code: ```rust use std::marker::PhantomData; #[derive(Clone, Copy)] pub struct TypedAddress<T>{ inner: u64, phantom: PhantomData<T>, } pub trait Memory { fn write_value<T>(&self, offset: TypedAddress<T>, value: &T); fn return_value<T>(&self, offset | labels: A-diagnostics, A-macros, T-compiler, A-suggestion-diagnostics, D-newcomer-roadblock", "label": "medium", "label_id": 2}
+{"id": "rust_145123", "text": "Performance regression with auto-vectorization from 1.87 onwards | ### Code I tried this code: ```rust pub fn unfilter_4(previous: &[u8], current: &mut [u8]) { let mut a_bpp = [0; 4]; let mut c_bpp = [0; 4]; for (chunk, b_bpp) in current.chunks_exact_mut(4).zip(previous.chunks_exact(4)) { let new_chunk = [ chunk[0].wrapping_a | labels: A-LLVM, T-compiler, regression-from-stable-to-stable, C-bug", "label": "critical_bug", "label_id": 0}
+{"id": "rust_152177", "text": "[ICE]: Compiler panic while compiling ppc64le rust code in linux tree | <!-- 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-PowerPC, C-bug", "label": "high", "label_id": 1}