Number 1 is a joke although achievable until certa...

# coroutines

[Pablichjenkov]

Number 1 is a joke although achievable until certain limits. Obviously System Process errors, JVM memory segments corruption, power failure or malfunctioning chips errors would not get even caught because probably the try-catch byte code for doing so is in trouble too.
I just googled the subject and it seems that the trend is what you just pointed out. A mixed of proper error handling plus let unthinkable errors explode.
Now in regards to what Adam said, what would be the danger in catching CancellationException?
Or better asked, what would be the right way to handle it.
I see the CancellationException as a passive Exception rather than a bad one. It let the parent coroutine know that one of the children is out and that's it.
Well, that if the CancellationException is empty. If it wraps another exception then don't know what is the standard pattern, should we always re-throw it to propagate up?