# \[Pitch N+1\] Typed Throws

**URL:** <https://forums.swift.org/t/pitch-n-1-typed-throws/67496>\
**Category:** Pitches\
**Created:** [September 25, 2023, 4:25am UTC](https://forums.swift.org/t/pitch-n-1-typed-throws/67496 "2023-09-25T04:25:05Z")\
**Posts on this page:** 1\
**Showing post:** 178

<div class="post-metadata">

**Author:** ![Karl](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@Karl](https://forums.swift.org/u/Karl)\
**Post date:** [October 2, 2023, 4:08pm UTC](https://forums.swift.org/t/pitch-n-1-typed-throws/67496/178 "2023-10-02T16:08:43Z")

</div>

> [@Design Priorities for the Swift 6 Language Mode](https://forums.swift.org/t/design-priorities-for-the-swift-6-language-mode/62408/1):
>
> Swift language version 6, which we'll refer to herein as Swift 6, offers an opportunity to introduce a targeted set of source-incompatible changes to the language. Swift 6 must not change the fundamental shape of the language, nor make sweeping changes without purpose. Rather, it should only introduce changes that serve a specific goal that benefits the entire Swift ecosystem and is not achievable while maintaining source compatibility.

> [@Design Priorities for the Swift 6 Language Mode](https://forums.swift.org/t/design-priorities-for-the-swift-6-language-mode/62408/1):
>
> The Language Workgroup will evaluate on a case-by-case basis any additional changes that provide sufficiently high value to the language relative to the cost of source incompatibilities they introduce. For example, Swift 6 may include proposals with source-incompatible changes where they are needed to finish a feature that cannot be completed otherwise, such as the regex literal parsing changes in [SE-0354](https://github.com/apple/swift-evolution/blob/main/proposals/0354-regex-literals.md) or the requirement for 'any' on existential types introduced in [SE-0335](https://github.com/apple/swift-evolution/blob/main/proposals/0335-existential-any.md).

I'm not really sure exactly what is being discussed here -- the removal of `rethrows`? Or just general observations that a similar concept may be expressible in another way? I read the discussion, but I still can't tell exactly.

If it is the former, I hope it comes with some very, very compelling reasons for breaking source compatibility. Especially since, as has been noted, this "other way" is not an exact 1:1 replacement for the existing `rethrows` feature. That means there may be libraries which cannot implement that other way without breaking their APIs.

---

_[View the full topic](https://forums.swift.org/t/pitch-n-1-typed-throws/67496)._
