[swift-evolution] Adding Result to the Standard Library

Chris Lattner clattner at nondot.org
Thu Nov 2 22:41:22 CDT 2017


> On Nov 2, 2017, at 11:08 AM, Jon Shier via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Swift-Evolution:
> 	I’ve written a first draft of a proposal to add Result<T> to the standard library by directly porting the Result<T> type used in Alamofire to the standard library. I’d be happy to implement it (type and tests for free!) if someone could point me to the right place to do so. I’m not including it directly in this email, since it includes the full implementation and is therefore quite long. (Discourse, please!) 
> 
> https://github.com/jshier/swift-evolution/blob/master/proposals/0187-add-result-to-the-standard-library.md <https://github.com/jshier/swift-evolution/blob/master/proposals/0187-add-result-to-the-standard-library.md>
I’m generally supportive of this, but the design of such a thing forces another contentious issue: whether the error handling model should be extended to support "typed throws”.  Without result, we can carry on pushing the "typed throws” debate down the road.  Adding it would force that issue to be decided, which is complicated.

-Chris


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20171102/c82a64d7/attachment.html>


More information about the swift-evolution mailing list