Search results

Private field can cause confusion with identically named field on a deref target

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149546 In rust-lang/rust;

· dvdsk opened on Dec 2, 2025

rustc crashes when trying to check if nested <code>type_ascription</code> constitutes a read of never

C-bugCategory: This is a bug.Category: This is a bug.

F-never_type`#![feature(never_type)]``#![feature(never_type)]`

F-type_ascription`#![feature(type_ascription)]``#![feature(type_ascription)]`

F-unsafe_binders`#![feature(unsafe_binders)]``#![feature(unsafe_binders)]`

I-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.

requires-nightlyThis issue requires a nightly compiler in some way.This issue requires a nightly compiler in some way.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149542 In rust-lang/rust;

· WaffleLapkin opened on Dec 2, 2025

f*::min/max do not behave as documented for signaling NaN on aarch64

A-floating-pointArea: Floating point numbers and arithmeticArea: Floating point numbers and arithmetic

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.

Status: Open.

#149537 In rust-lang/rust;

· RalfJung opened on Dec 2, 2025

compiletest panics with inscrutable error message when invoked the wrong way

A-compiletestArea: The compiletest test runnerArea: The compiletest test runner

C-bugCategory: This is a bug.Category: This is a bug.

T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149523 In rust-lang/rust;

· RalfJung opened on Dec 1, 2025

<code>no_mangle_const_items</code>: <code>const</code> -&gt; <code>pub static</code> suggestion causes syntax error

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

A-suggestion-diagnosticsArea: Suggestions generated by the compiler applied by `cargo fix`Area: Suggestions generated by the compiler applied by `cargo fix`

D-invalid-suggestionDiagnostics: A structured suggestion resulting in incorrect code.Diagnostics: A structured suggestion resulting in incorrect code.

E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

F-generic_const_items`#![feature(generic_const_items)]``#![feature(generic_const_items)]`

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149511 In rust-lang/rust;

· matthiaskrgr opened on Dec 1, 2025

Confusing #warn(unused_comparisons)

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149490 In rust-lang/rust;

· skvadrik opened on Nov 30, 2025

Diagnostic for .unwrap_or_default() suggests removing unrelated code

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149487 In rust-lang/rust;

· nabijaczleweli opened on Nov 30, 2025

Array indexed by exhaustive match still generates bounds checks

C-optimizationCategory: An issue highlighting optimization opportunities or PRs implementing suchCategory: An issue highlighting optimization opportunities or PRs implementing such

needs-triageThis issue may need triage. Remove it if it has been sufficiently triaged.This issue may need triage. Remove it if it has been sufficiently triaged.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149480 In rust-lang/rust;

· Arnavion opened on Nov 30, 2025

ICE when reusing <code>syn::Error</code> stored in static <code>LazyLock</code> across multiple proc macro invocations

A-proc-macrosArea: Procedural macrosArea: Procedural macros

C-bugCategory: This is a bug.Category: This is a bug.

I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️

needs-triageThis issue may need triage. Remove it if it has been sufficiently triaged.This issue may need triage. Remove it if it has been sufficiently triaged.

S-has-mcveStatus: A Minimal Complete and Verifiable Example has been found for this issueStatus: A Minimal Complete and Verifiable Example has been found for this issue

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149465 In rust-lang/rust;

· mookums opened on Nov 29, 2025

Error for <code>for let mut v = vec![]; v.push(v);</code> ‒ "error[E0275]: overflow assigning <code>Vec&lt;_&gt;</code> to <code>_</code>" ‒ seems poor

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149464 In rust-lang/rust;

· nabijaczleweli opened on Nov 29, 2025

Using maybe-sized APIT in <code>async fn</code> produces duplicate E0277 diagnostic

A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lints

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149439 In rust-lang/rust;

· obi1kenobi opened on Nov 29, 2025

doctests: print_merged_doctests_times() crashes JUnit formatter

C-bugCategory: This is a bug.Category: This is a bug.

I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️

needs-triageThis issue may need triage. Remove it if it has been sufficiently triaged.This issue may need triage. Remove it if it has been sufficiently triaged.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#149436 In rust-lang/rust;

· ilammy opened on Nov 29, 2025