Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Child work belongs to a defined parent lifetime rather than becoming untracked background work. Cancellation and failures follow the chosen task or coroutine hierarchy.
A feature should await or otherwise manage work it starts, release resources on cancellation, and define whether sibling failures cancel other work. Exact propagation depends on the concurrency construct, such as supervised versus regular coroutine scopes. Cancellation is cooperative: blocking operations and loops may need explicit support. Avoid detached work unless its independent ownership is intentional.