@bj0 we'll have a new release of

kotlinx.coroutines

when Kotlin 1.2.30 is out. The plan is to have

isActive

extension on

CoroutineContext

, so that you can use

coroutineContext.isActive

. The open question is whether

CoroutineScope

shall be completely deprecated and slated for removal or should we leave

isActive

"shortcut" in the

CoroutineScope

?

@elizarov I'd go with either

coroutineContext.isActive

, or

isCurrentCoroutineActive

, or both, with a complete

CoroutineScope

deprecation.