Atul Gupta
08/18/2024, 9:35 PMcurrentCoroutineContext()
over coroutineContext
always good? Shouldn't we then deprecate the coroutineContext
suspending variable or make it internal? I am asking as having multiple similar methods unnecessarily increase the cognitive overloadephemient
08/18/2024, 9:47 PMAtul Gupta
08/19/2024, 8:18 AMcurrentCoroutineContext()
) over the other? Especially when using Coroutines in an application
Also are you trying to say that since both of these exists in different libs we can't deprecate one in favour of the other?ephemient
08/19/2024, 8:22 AMcoroutineContext
because it is necessary for things using the kotlin.coroutines
infrastructure (such as SequenceBuilder
)
but it's confusing in kotlinx.coroutines
(note the x
), which is probably what you're working with more often