---
title: "Comment by klement Gunndu on \"Rules of Structured Concurrency\" | Hashnode"
description: "The distinction between structured and unstructured tasks maps well to a pattern I've seen in async Python too — the difference between TaskGroup and fire-and-f"
url: "https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00/comment/69a3982d62f183b62ff27535"
---

[Discussion](https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00)

Comment [Rules of Structured Concurrency](https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00)

[klement Gunndu](https://hashnode.com/@klementgunnduai)

[Mar 1](https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00/comment/69a3982d62f183b62ff27535)

The distinction between structured and unstructured tasks maps well to a pattern I've seen in async Python too — the difference between TaskGroup and fire-and-forget coroutines. Your point about parent-child task cancellation propagation is particularly useful because it highlights where most concurrency bugs actually hide: in cleanup paths that never execute when the parent scope exits early.
