[swift-evolution] typed throws
ckornher at me.com
Fri Aug 18 13:03:20 CDT 2017
> On Aug 18, 2017, at 7:38 AM, Matthew Johnson via swift-evolution <swift-evolution at swift.org> wrote:
> I would like to reiterate the point I made in the question that spawned this thread: there are *many* Swift libraries for writing async code of various sorts which are *already* using typed errors via `Result<Value, ErrorType: Error>`. We don't have to speculate about how this feature might be used and what kind of benefits might be realized. We can have a discussion about what people are already doing and determine whether this model should be supported in the async / await world or not. What do you think of putting a call out to the broader Swift community to bring us concrete examples of how they are benefiting from using typed errors in async code.
I have found this “feature" has been painful to use. I have been forced to wrap hetrogenous errors in a custom error type just to satisfy these ill-conceived APIs. i have never found any benefit to ```ErrorType: Error``` generic parameter. … Any. Ever.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution