You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Compiler panic on explicit tail calls (become) #5131
The compiler panics on explicit tail calls (become, feature explicit_tail_calls), inside rustc_public.
#![feature(explicit_tail_calls)]#![allow(incomplete_features)]fng(x:u32) -> u32{
x + 1}fnf(x:u32) -> u32{become g(x)}#[kani::proof]fntail_call(){assert_eq!(f(1),2);}
thread 'rustc' panicked at .../compiler/rustc_public/src/unstable/convert/stable/mir.rs:775:79:
not implemented
rustc_public doesn't convert the TailCall terminator. The feature is unstable and incomplete, so a clear "unsupported" error would do for now. Found with Miri's fail/tail_calls/dangling-local-var.rs. Kani 0.68.0 at main (47689dc), CBMC 6.11.0.
rustc_public has no TailCall terminator variant, so converting a body containing one reaches unimplemented!(). Kani loaded these bodies without checking for explicit tail calls first.
The diff checks internal MIR before body conversion during transformation, proof metadata generation, and autoharness processing, including instantiation search. It reports each explicit tail call in the body at its source span and aborts with an unsupported-feature diagnostic.
Activity
mvanhorn commentedon Nov 11, 2026
rustc_publichas noTailCallterminator variant, so converting a body containing one reachesunimplemented!(). Kani loaded these bodies without checking for explicit tail calls first.The diff checks internal MIR before body conversion during transformation, proof metadata generation, and autoharness processing, including instantiation search. It reports each explicit tail call in the body at its source span and aborts with an unsupported-feature diagnostic.
#5152
Report explicit tail calls as unsupported instead of panicking (model…