Some prior, probably not as well thought-through, discussion on this topic: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160229/011446.html On Wed, Jul 5, 2017 at 10:40 AM Soroush Khanlou via swift-evolution < swift-evolution@swift.org> wrote:
> I’d like to propose a guard/catch construct to the language. It would > allow code to use throwing functions and handle errors fully, without > straying from a happy path. do/catch can be a bit heavy-handed sometimes, > and it would be nice to be able to handle throwing functions without > committing to all the nesting and ceremony of do/catch. > > Full proposal, which discusses all the corner cases and alternatives: > https://gist.github.com/khanlou/8bd9c6f46e2b3d94f0e9f037c775f5b9 > > Looking forward to feedback! > > Soroush > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
