[swift-evolution] [Proposal Idea] catching functions for composable and cps error handling
matthew at anandabits.com
Thu Dec 17 09:01:55 CST 2015
I am definitely interested in seeing your proposal if you’ve already written it.
Async / concurrency, etc is explicitly out of scope. I think features like catching functions which have applications in asynchronous code but do not specifically address concurrency, synchronization, etc are at least worth discussing unless / until the core team specifically rules them out. My thought is that catching functions could be a natural evolution of the error handling introduced in Swift 2.
> On Dec 16, 2015, at 11:42 PM, Brent Royal-Gordon <brent at architechies.com> wrote:
>> The basic idea is to allow catching functions that would be a complement to throwing functions.
> I have an enormous proposal on the subject of formalizing completion handlers which includes catching functions. I haven’t posted it because I figured it’d be out of scope for Swift 3, but I can if there’s interest.
> Brent Royal-Gordon
More information about the swift-evolution