I’m curious about the example in the coroutines guide for structured concurrency on Android : ``` ab...

# coroutines

[Martin Devillers]

I’m curious about the example in the coroutines guide for structured concurrency on Android :

abstract class ScopedAppActivity: AppCompatActivity(), CoroutineScope {
    protected lateinit var job: Job
    override val coroutineContext: CoroutineContext 
        get() = job + Dispatchers.Main
    
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        job = Job()
    }
        
    override fun onDestroy() {
        super.onDestroy()
        job.cancel()
    } 
}

https://github.com/Kotlin/kotlinx.coroutines/blob/master/ui/coroutines-guide-ui.md#structured-concurrency-lifecycle-and-coroutine-parent-child-hierarchy
It seems to me that this example is needlessly complicated. The following would work just as well.

abstract class ScopedAppActivity: AppCompatActivity(), CoroutineScope {
    override val coroutineContext: CoroutineContext = Job()

    override fun onDestroy() {
        super.onDestroy()
        coroutineContext[Job]?.cancel()
    }
}

Since Dispatchers.Main is the ContinuationInterceptor used when none is available in a CoroutineContext, this should yield the same result. Is there something I’m missing?

[Pavel.AZ]

may be override val coroutineContext: CoroutineContext = Job() + Dispatchers.Main ?

[Martin Devillers]

That’s kind of my thought as well…