In consts, values with destructors can be lifetime-extended into statics.

I'm not sure if this is a bug or not.

struct Thing;

impl Drop for Thing {
    fn drop(&mut self) {
        println!("drop");
    }
}

const X: &Thing = &Thing;

fn main() {
    let _a = X;
}

The above code prints nothing. It seems that the Thing value is lifetime-extended into an implicit static.

I believe that the design intention of const is that replacing a const with its definition should not change its behavior. However, in the above code, replacing X with &Thing causes it to print drop. Therefore, I think this code should probably produce a compile error.

Meta

Reproducible on the playground with version 1.91.0-nightly (2025-08-25 54c581243c977c7662c9)

Reproduce the example in the Rust Playground using the reported nightly version, then compare the const-based code with the inline &Thing form. Read the Rust Reference section on destructor lifetime extension into statics and determine whether the differing drop behavior should be rejected; done means the language behavior and intended diagnostic are agreed and covered by a regression test.