This doesn't have anything to do with exceptions, and the context appears to be Zig, not Rust.
The article is about how we represent errors not their control flow (i.e., exceptions).
The article is about how we represent errors not their control flow (i.e., exceptions).
"Instead, when returning an error, rather than jumping to the return address, we look it up in the side table to find a corresponding error recovery address, and jump to that. Stack unwinding!
The bold claim is that unwinding is the optimal thing to do! .."
My opinion (which one need not approve of) is that it asymptotically approaches the language-level control flow constructs.