Conversation

Notices

1. Embed this notice
   Doug Gregor (dgregor79@sfba.social)'s status on Tuesday, 16-Jan-2024 07:56:09 JST Doug Gregor

   Finally landed the first of many #SwiftLang standard library updates to replace "rethrows" with generic typed throws: https://github.com/apple/swift/pull/69771. The feature has been a fantastic exercise in generalizing in place: it maintains the same behavior for existing Swift code, maintains the stable ABI of the standard library, and yet any Swift code that adopts typed throws will see typed errors propagate through the standard library in the natural way.

   • Embed this notice
     Paul Cantrell (inthehands@hachyderm.io)'s status on Tuesday, 16-Jan-2024 07:57:38 JST Paul Cantrell

     in reply to

     @dgregor79 Still love this work and how the proposal landed in the end. A real software community success story!

   • Embed this notice
     Doug Gregor (dgregor79@sfba.social)'s status on Tuesday, 16-Jan-2024 07:57:39 JST Doug Gregor

     in reply to

     If you're interested in how typed throws manages to generalize #SwiftLang's error handling to provide more expressive APIs, check out the accepted design proposal at https://github.com/apple/swift-evolution/blob/main/proposals/0413-typed-throws.md.

   • Embed this notice
     Doug Gregor (dgregor79@sfba.social)'s status on Tuesday, 16-Jan-2024 07:57:40 JST Doug Gregor

     in reply to

     Another, simpler example is Swift's Result type, which has always effectively had typed errors because it's generic over the "Failure" type. However, any interaction between Result and errors in the language (e.g., an actual throw or do..catch) would have to erase to "any Error". Now, we can express the relationship between the "Failure" type and error handling, allowing one to smoothly go between throw/do..catch and Result: https://github.com/apple/swift/pull/70907