In your example, I don't see any, which is great. But async can have hidden control flow. (I wonder why Andrew Kelley added it when he is so against even hidden function calls.)
On top of that, I don't think async is a good paradigm, but that's neither here or there to the conversation.
Ie. Zig's error system which is not based on algebraic effects is best in class.
Async does carry that same cost, but it comes with capabilities you can't get otherwise and is optional. Any objections to it are a demonstration of my point, not a disagreement with it.
Exceptions are better than async because they do not "reify" stack frames, an incredibly terrible idea. I mean, it works, but it's not a good model, mentally or otherwise.
Then you put your value behind the error in the type...like rust or zig where you cannot ignore them.
You keep describing the upsides of Zig's error system as reasons why something else is better.
Here's my best attempt at demonstrating conditions and restarts with zig-native tools.
Edit: fixed my dumb. https://zig.godbolt.org/z/creoT47Mj
Note that it'd get substantially more erganomic if yield were finished with all of the usual niceties of the monad-ish error keywords.
Also edit: Upon further reflection to be actually correct conditions/restarts, you'd have to unwind starting from inside the inner function if the handler gave up. This is doable by passing some state back down (handled/unhandled) from the outer scope, and then just returning an error from the bottom scope to begin either unwinding or let a non-restartable error handling mechanism do its thing.
Additionally I don't think this is compatible with also using async for its intended purpose without comptime shenanigans.