---
title: "Comment by Fabio Sarmento on \"Rules of Structured Concurrency\" | Hashnode"
description: "While working on a recent project, I encountered a scenario where using structured concurrency significantly simplified my error handling. By leveraging async l"
url: "https://hashnode.com/posts/rules-of-structured-concurrency/67f2bb1049ea7db6aa9cbd00/comment/69be8f743800d823983c6150"
---

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

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

[Fabio Sarmento](https://hashnode.com/@sarmento)

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

While working on a recent project, I encountered a scenario where using structured concurrency significantly simplified my error handling. By leveraging `async let` and task groups, I was able to manage multiple asynchronous calls seamlessly, ensuring that all tasks completed before proceeding. It was a clear reminder of how adopting a structured approach can lead to cleaner, more maintainable code.
