Are there are drawback to the `currentCoroutineContext()` function? I want to cancel my listener whe...

# coroutines

[Alexandru Hadăr]

Are there are drawback to the currentCoroutineContext() function?
I want to cancel my listener when my coroutine is no longer active. I don’t have access to the scope, but I can use currentCoroutineContext() since i’m inside a suspend function. Could this have any negative impact? Like memory leak or a false-positive?

private suspend fun doEffects(colorChangeCallback: OnColorChangedCallback, valueAnimator: ValueAnimator) {
    val context: CoroutineContext = currentCoroutineContext()
    valueAnimator.addUpdateListener {
        if (context.isActive) {
            // Do your work
        } else {
            // Cancel other work
            valueAnimator.cancel()
        }
    }
}

[Dmitry Khalanskiy [JB]]

See this thread from yesterday: https://kotlinlang.slack.com/archives/C1CFAFJSK/p1652964299132039
If you're outside of a coroutine (for example, if you call your function from suspend fun main), currentCoroutineContext will be empty.

[Alexandru Hadăr]

Thanks, I’ll look into it

[julian]

Why not use suspendCancellableCoroutine and invokeOnCancellation?

[Alexandru Hadăr]

Did not know of it