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?

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).

one is from the kotlin stdlib

the other is from kotlinx.coroutines