Rust project goal pushes for stable explicit tail calls — but it will take money and time

What’s happening

It has been reported that Folkert de Vries and a contributor known as Waffle have submitted a Rust project goal to push explicit tail calls forward during 2026. The aim is modest: not full stabilization this year, but lining things up so explicit tail calls could be stabilized in 2027. It has been reported that the effort needs funding — and the authors are asking teams that rely on guaranteed tail calls (or would benefit from them) to step up.

Why tail calls matter

A tail call is a function call that reuses the caller’s stack frame, enabling recursion without risking stack overflow. In Rust the experimental explicit-tail-call feature exposes a become keyword so a function can insist its final call is compiled as a tail call; callers and callees must agree on calling semantics (hence the same-signature restriction). That might look like a small nicety on the surface. But for low-level systems work it’s a different animal: tail calls let you write compact, highly controllable codegen patterns — jump-table-driven state machines, interpreters, lexers and decoders — without dropping into assembly. Think of it as getting the precision of hand-written jumps with the safety and portability of Rust. Neat, right?

What comes next

The project goal lays out the engineering path for 2026 and hopes to land stabilization in 2027 if momentum (and funding) allow. The emotional hook here: for a lot of systems programmers this is the sort of incremental language work that unlocks huge practical wins — fewer hacks, faster state machines, predictable performance. Will the community fund it and turn experimental become into a stable primitive? That’s the question now. If you care about efficient, maintainable low-level code, the authors want to hear from you.

Sources: trifectatech.org, Lobsters