kotlin-coroutines-structured-concurrency

Storing a CoroutineScope in a class often causes leaks because the scope outlives the intended lifecycle. You should convert public APIs to suspend functions and relate launches to a clear lifecycle boundary with proper cancellation handling.

Structured concurrency in Kotlin ensures child coroutines are tied to a specific lifecycle and cannot outlive their parent scope. This prevents unstructured concurrency by enforcing proper cancellation handling and error propagation, avoiding fire-and-forget calls and unmanaged launches.

To refactor init-time launches, migrate them to explicit bootstrapping points with clear lifecycle boundaries. Convert class-wide CoroutineScope properties to suspend functions to ensure proper scope ownership and safe cancellation handling.

Using fire-and-forget calls with non-suspending APIs creates unstructured concurrency and risks leaks. You should convert public APIs to suspend functions and relate launches to a clear lifecycle boundary for proper error propagation.

Best practices for Kotlin coroutine scope management include avoiding stored scopes in classes, converting public APIs to suspend, and binding launches to explicit lifecycle boundaries. This ensures proper cancellation handling and prevents leaks.