Kotlin coroutines' cancellation behavior: how does it affect structured concurrency?

25 Haz 07:00

Whenever a coroutine is cancelled, the cancellation propagates through its hierarchy. I’m trying to understand how this propagation influences structured concurrency rules, especially when multiple child coroutines are involved. Does a cancellation of the parent always terminate all children instantly, or can they finish their current work before stopping? Also, what are the best practices to handle cleanup and resource release in such scenarios? Would love to hear explanations or examples from the community.