ICE from using `super let` and `&raw` in `const`

Nobody has claimed this yet.

Code

#![feature(super_let)]

const _: *const i32 = {
    super let x = 1;
    &raw const x
};

Error output

error: internal compiler error: compiler/rustc_const_eval/src/interpret/intern.rs:285:21: the static const safety checks accepted mutable references they should not have accepted
 --> src/lib.rs:3:1
  |
3 | const _: *const i32 = {
  | ^^^^^^^^^^^^^^^^^^^

Backtrace

thread 'rustc' panicked at compiler/rustc_const_eval/src/interpret/intern.rs:285:21:
Box<dyn Any>
stack backtrace:
   0: std::panicking::begin_panic::<rustc_errors::ExplicitBug>
   1: <rustc_errors::diagnostic::BugAbort as rustc_errors::diagnostic::EmissionGuarantee>::emit_producing_guarantee
   2: <rustc_errors::DiagCtxtHandle>::span_bug::<rustc_span::span_encoding::Span, alloc::string::String>
   3: rustc_middle::util::bug::opt_span_bug_fmt::<rustc_span::span_encoding::Span>::{closure#0}
   4: rustc_middle::ty::context::tls::with_opt::<rustc_middle::util::bug::opt_span_bug_fmt<rustc_span::span_encoding::Span>::{closure#0}, !>::{closure#0}
   5: rustc_middle::ty::context::tls::with_context_opt::<rustc_middle::ty::context::tls::with_opt<rustc_middle::util::bug::opt_span_bug_fmt<rustc_span::span_encoding::Span>::{closure#0}, !>::{closure#0}, !>
   6: rustc_middle::util::bug::span_bug_fmt::<rustc_span::span_encoding::Span>
   7: rustc_const_eval::interpret::intern::intern_const_alloc_recursive::<rustc_const_eval::const_eval::machine::CompileTimeMachine>
   8: rustc_const_eval::const_eval::eval_queries::eval_to_allocation_raw_provider
      [... omitted 1 frame ...]
   9: rustc_const_eval::const_eval::eval_queries::eval_to_const_value_raw_provider
      [... omitted 1 frame ...]
  10: rustc_hir_analysis::check_crate
  11: rustc_interface::passes::analysis
      [... omitted 1 frame ...]
  12: rustc_interface::passes::create_and_enter_global_ctxt::<core::option::Option<rustc_interface::queries::Linker>, rustc_driver_impl::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0}
  13: rustc_interface::interface::run_compiler::<(), rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: please make sure that you have updated to the latest nightly

note: please attach the file at `/playground/rustc-ice-2025-06-09T05_51_22-61.txt` to your bug report

note: compiler flags: --crate-type lib -C embed-bitcode=no -C codegen-units=1 -C debuginfo=2

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
#0 [eval_to_allocation_raw] const-evaluating + checking `_`
#1 [eval_to_const_value_raw] simplifying constant for the type system `_`
#2 [analysis] running analysis passes on this crate
end of query stack
error: could not compile `playground` (lib)

Reproduce the ICE with the minimal example using the reported nightly compiler, then inspect compiler/rustc_const_eval/src/interpret/intern.rs around the reported assertion. Trace the const-evaluation path shown in the backtrace and determine the expected handling for this input. Done means the example no longer triggers an internal compiler error and coverage exists for the regression.

Written by the indexing model from the issue text.

Description

Code

Meta

Error output

Contributor guide

First steps

Research direction

Assessment

ICE from using `super let` and `&raw` in `const`

Description

Code

Meta

Error output

Contributor guide

First steps

Research direction

Assessment

Get new issues in your inbox