---
title: "Comment by Mm Cc on \"Rules of Structured Concurrency\" | Hashnode"
description: "Great breakdown of structured vs. unstructured tasks! A tip: when you do need to escape the structured hierarchy with an unstructured task (like in a legacy del"
url: "https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00/comment/69f89bafb4a68c1fb2d4c403"
---

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

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

[Mm Cc](https://hashnode.com/@mmcc)

[May 4](https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00/comment/69f89bafb4a68c1fb2d4c403)

Great breakdown of structured vs. unstructured tasks! A tip: when you _do_ need to escape the structured hierarchy with an unstructured task (like in a legacy delegate callback), explicitly capture a weak reference to the parent context to avoid accidental strong reference cycles—especially if the task outlives the parent’s lifecycle.