# SE-0296: async/await

**URL:** <https://forums.swift.org/t/se-0296-async-await/42605>\
**Category:** Proposal Reviews\
**Created:** [December 8, 2020, 6:23pm UTC](https://forums.swift.org/t/se-0296-async-await/42605 "2020-12-08T18:23:26Z")\
**Posts on this page:** 1\
**Showing post:** 37

<div class="post-metadata">

**Author:** ![anandabits](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/anandabits/32/355_2.png) [@anandabits](https://forums.swift.org/u/anandabits)\
**Post date:** [December 10, 2020, 2:03am UTC](https://forums.swift.org/t/se-0296-async-await/42605/37 "2020-12-10T02:03:04Z")

</div>

> [@Douglas\_Gregor](#):
>
> That's not the design of cancellation described in the Structured Concurrency proposal. A potential suspension point is not a return point. One manually checks for cancellation and can then choose to exit early via either of the normal mechanisms, whether it's `return` or `throw` . Cancellation is not a third kind of exit.

I know it’s off topic for this thread, but I have asked for a more clear justification of this approach to cancellation and none has been provided thus far. Given that Structured Concurrency is a pitch and not an accepted proposal, I don’t think reviewers of async / await should be expected to accept its design as a given. There is more discussion to be had around cancellation before a final design is accepted.

---

_[View the full topic](https://forums.swift.org/t/se-0296-async-await/42605)._