rust/tests/ui/consts/precise-drop-with-promoted.rs

// Regression test for issue #89938.
//@ check-pass
//@ compile-flags: --crate-type=lib

#![feature(const_precise_live_drops)]

pub const fn f() {
    let _: Option<String> = None;
    let _: &'static Option<String> = &None;
}
Fix const qualification when executed after promotion The const qualification was so far performed before the promotion and the implementation assumed that it will never encounter a promoted. With `const_precise_live_drops` feature, checking for live drops is delayed until after drop elaboration, which in turn runs after promotion. so the assumption is no longer true. When evaluating `NeedsNonConstDrop` it is now possible to encounter promoteds. Use type base qualification for the promoted. It is a sound approximation in general, and in the specific case of promoteds and `NeedsNonConstDrop` it is precise. 2021-10-19 00:00:00 +00:00			`// Regression test for issue #89938.`
Fix const drop checking 2023-12-06 22:01:21 +00:00			`//@ check-pass`
Fix const qualification when executed after promotion The const qualification was so far performed before the promotion and the implementation assumed that it will never encounter a promoted. With `const_precise_live_drops` feature, checking for live drops is delayed until after drop elaboration, which in turn runs after promotion. so the assumption is no longer true. When evaluating `NeedsNonConstDrop` it is now possible to encounter promoteds. Use type base qualification for the promoted. It is a sound approximation in general, and in the specific case of promoteds and `NeedsNonConstDrop` it is precise. 2021-10-19 00:00:00 +00:00			`//@ compile-flags: --crate-type=lib`
update tests, adding known-bug 2023-07-27 15:51:02 +00:00
Fix const qualification when executed after promotion The const qualification was so far performed before the promotion and the implementation assumed that it will never encounter a promoted. With `const_precise_live_drops` feature, checking for live drops is delayed until after drop elaboration, which in turn runs after promotion. so the assumption is no longer true. When evaluating `NeedsNonConstDrop` it is now possible to encounter promoteds. Use type base qualification for the promoted. It is a sound approximation in general, and in the specific case of promoteds and `NeedsNonConstDrop` it is precise. 2021-10-19 00:00:00 +00:00			`#![feature(const_precise_live_drops)]`

			`pub const fn f() {`
			`let _: Option<String> = None;`
			`let _: &'static Option<String> = &None;`
			`}`