I don't remember there being two `CancellationExceptions`... They're not aliases of each other... Do...

# coroutines

[Sam]

I don't remember there being two CancellationExceptions... They're not aliases of each other... Does either one work?

[Sam]

I guess my actual question is how I can have a coroutine cancel itself. I was thinking to just throw CancellationException(...), but it looks like coroutineContext.cancel(...); ensureActive() might be more correct?

[Trevor Stone]

yes calling cancel is the correct way

[Sam]

Okay, cool, thanks

[Sam]

It still would be useful to know why there are two exception classes though... It does come up when trying to exclude CancellationException from a catch block (I guess I could check for both).

[Trevor Stone]

On the JVM they are both typealias of java.util.concurrent.CancellationException I believe

[Trevor Stone]

one is from the kotlin stdlib

[Trevor Stone]

the other is from kotlinx.coroutines

[Sam]

Ah, gotcha. I figured it might be like that. Thanks!