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 affects structured concurrency rules, especially when dealing with multiple child coroutines. Does cancelling the parent always terminate all children immediately, or can they finish their current work before stopping? Also, what are the best practices for handling cleanup and resource release in these scenarios? Would love to hear explanations or examples from the community.