# Precise error typing in Swift

**URL:** <https://forums.swift.org/t/precise-error-typing-in-swift/52045>\
**Category:** Discussion\
**Tags:** error-handling\
**Created:** [September 14, 2021, 9:24am UTC](https://forums.swift.org/t/precise-error-typing-in-swift/52045 "2021-09-14T09:24:56Z")\
**Posts on this page:** 1\
**Showing post:** 88

<div class="post-metadata">

**Author:** ![Sajjon](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/sajjon/32/12044_2.png) [@Sajjon](https://forums.swift.org/u/Sajjon)\
**Post date:** [September 12, 2022, 10:29am UTC](https://forums.swift.org/t/precise-error-typing-in-swift/52045/88 "2022-09-12T10:29:14Z")

</div>

What is the status of this? It was linked to by @hborla in the [thread about Primary Associated Types in the context of getting support for them for AsyncSequence](https://forums.swift.org/t/se-0346-lightweight-same-type-requirements-for-primary-associated-types/55869/70) - which is something I'm very much looking forward to.

So precise error typing is potentially blocking PATs for AsyncSequence, and I got a bit worried that `AsyncSequence<Element>` support might be delayed a lot until we see some progress in this thread?

Thx!

---

_[View the full topic](https://forums.swift.org/t/precise-error-typing-in-swift/52045)._
