5cc83fd4a5
THIR unsafety checking was getting a cycle of function unsafety checking -> building THIR for the function -> evaluating pattern inline constants in the function -> building MIR for the inline constant -> checking unsafety of functions (so that THIR can be stolen) This is fixed by not stealing THIR when generating MIR but instead when unsafety checking. This leaves an issue with pattern inline constants not being unsafety checked because they are evaluated away when generating THIR. To fix that we now represent inline constants in THIR patterns and visit them in THIR unsafety checking.
30 lines
691 B
Rust
30 lines
691 B
Rust
// edition:2018
|
|
// revisions: mir thir
|
|
// [thir]compile-flags: -Z thir-unsafeck
|
|
|
|
struct S;
|
|
|
|
impl S {
|
|
async unsafe fn f() {}
|
|
}
|
|
|
|
async unsafe fn f() {}
|
|
|
|
async fn g() {
|
|
S::f();
|
|
//[mir]~^ ERROR call to unsafe function is unsafe
|
|
//[thir]~^^ ERROR call to unsafe function `S::f` is unsafe
|
|
f();
|
|
//[mir]~^ ERROR call to unsafe function is unsafe
|
|
//[thir]~^^ ERROR call to unsafe function `f` is unsafe
|
|
}
|
|
|
|
fn main() {
|
|
S::f();
|
|
//[mir]~^ ERROR call to unsafe function is unsafe
|
|
//[thir]~^^ ERROR call to unsafe function `S::f` is unsafe
|
|
f();
|
|
//[mir]~^ ERROR call to unsafe function is unsafe
|
|
//[thir]~^^ ERROR call to unsafe function `f` is unsafe
|
|
}
|