> The argument here is against a core language feature and has nothing to do with async/await. Sure, guarded catch statements would be nice, but I contend that

> The argument here is against a core language feature and has nothing to do with async/await. Sure, guarded catch statements would be nice, but I contend that if you're relying on multiple levels of exception handling then you're using exceptions for flow control. I don't see how this is a problem. Try/Catch are by definition flow control keywords. Also, when you get an exception you have to differentiate between how you recover from it or package it into something that can be logged or used by a higher level caller. That said, I don't disagree with any of your other statements.