Shouldn't exceptions thrown in a suspend function bubble up like regular exceptions? Trying to catch...

# coroutines

[reactormonk]

Shouldn't exceptions thrown in a suspend function bubble up like regular exceptions?
Trying to catch a lower one, but it's not properly registered, just aborts the program
... err, works.

[Big Chungus]

That's only true if you're using supervisor scope

[reactormonk]

Wait, what? Exceptions behave differently than with regular functions?

[Big Chungus]

Yes, an exception thrown in sibling job will cancel parent job unless you're in supervisor scope

[Big Chungus]

Concurrent programming is different by nature, so it makes sense that some constructs would behave differently

[reactormonk]

I'm talking about a child function here.

[Big Chungus]

Same thing

[Big Chungus]

Watch some "coroutine exception handling" videos on youtube to get a better grasp

[reactormonk]

So

suspend fun a() { suspendCoroutine { block -> block.resumeWithException(IOException()) } }

suspend fun b() { try { a() } catch (e: IOException) { println(e) }

Won't catch the exception?

[Big Chungus]

No unless you use supervisor scope

[reactormonk]

So there's no error channel by default?

[reactormonk]

... and all exceptions cancel everything by default?

[reactormonk]

... weird design decision.

[reactormonk]

I guess I've been coddled too much with Scala Tasks.

[Big Chungus]

Not quite

[Big Chungus]

There are dedicated concurrent ways of handling exceptions

[Big Chungus]

Also there's a good reason behind this decision

[Big Chungus]

I found this explanation by @Lukas Lechner very helpful

https://youtu.be/coq9XDMB-yU?t=479▾

[reactormonk]

Yeah, videos ain't my thing, currently on https://www.lukaslechner.com/why-exception-handling-with-kotlin-coroutines-is-so-hard-and-how-to-successfully-master-it/

[Big Chungus]

I found the visuals there quite helpful, but to each its own i guess

[reactormonk]

So if I want an error channel, I can a) add a coroutineScope { try ... } or b) start using suspend fun a(): Result() and manually pass things along?

[Nick Allen]

@Big Chungus, you seem to be confusing the just calling a suspend method and launching a child coroutine.

@reactormonk Exceptions work with suspend methods just like they do for regular methods. Uncaught exceptions bubble up and caught exceptions are stopped. You can see an example here of exceptions working just as you expect.

Exceptions become more complicated if you are launching concurrent coroutines. For example:

try {
   launch { a() }
} catch (e: IOException) {}

would not catch anything because the exception is in a different coroutine than the one catching so it's not part of the same conceptual call stack.

[reactormonk]

kk, makes sense. I was doubting the sanity of the designers.

[Big Chungus]

@Nick Allen guilty as charged. Just rewatched the video I've linked to realize exactly that.