I enjoy Swift’s version of this, where you mark if a function can throw and you need to mark the callers up the chain until you handle those errors.
There’s also Haskell’s system, which IIRC uses an IO monad.
There’s also Haskell’s system, which IIRC uses an IO monad.
https://www.academia.edu/71720554/A_Modular_Verifiable_Excep...
So here you go, http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p070...
As for being useless, well that is the usual argument from no exception, no RTTI folks, that would be better off using another language instead of messing up with C++'s design.
The advantage of something like JavaScript's async/await over Haskell's "do" is the fact because async/await is more limited than `do` (or yield and coroutines in JS) it's a lot easier to create tooling for.
I really don’t get how is Haskell “behind”.
What kind of tooling are you referring to?