`&raw const` gets static-promoted in match guard

I tried this code:

static X: &i32 = unsafe {
    let wut = &*'a: {
        match one() {
            temp if { break 'a &raw const temp } => {}
            _ => {}
        }
        loop {}
    };
    wut
};

const fn one() -> i32 {
    1
}

fn main() {
    println!("{X}");
}

I expected some kind of error, possibly UB. Instead, the code runs fine and prints 1.

It seems that the &raw const temp is somehow causing temp to be lifetime-extended. This seems wrong. Only non-raw referencing should cause lifetime extension or static promotion.

See also https://github.com/rust-lang/rust/issues/142229, where a similar weirdness causes an ICE. cc @RalfJung

This issue was discovered jointly with @danielhenrymantilla

@rustbot labels +A-const-eval +A-patterns

Meta

Reproducible on the rust playground with version 1.91.0-nightly (2025-08-03 f34ba774c78ea32b7c40)

Start with the standalone Rust reproducer and the compiler areas covered by the A-const-eval and A-patterns labels. Determine why the raw const reference in the match guard is lifetime-extended or statically promoted, then add a regression test showing the expected behavior and run the relevant compiler tests.