<div dir="ltr">+1. The potential integration with auto-async-conversion here is brilliant and will be incredibly useful if implemented.<br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Mar 14, 2016 at 8:15 AM Thomas Guthrie via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><blockquote type="cite">On 14 Mar 2016, at 11:36, Ondrej Barina via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br>it would be great usage of Result. (there was discussion about it. I<br>think it was rejected).<br><br>Not really sure about: "let a: Result<Foo> = makeFoo(42)"<br>I can see that this could become more needed/used when we are going<br>towards async coding in next Swift (4.0?).<br></blockquote><br></div><div style="word-wrap:break-word">Result is mentioned in <a href="https://github.com/apple/swift/blob/master/docs/ErrorHandling.rst#manual-propagation-and-manipulation-of-errors" target="_blank">https://github.com/apple/swift/blob/master/docs/ErrorHandling.rst#manual-propagation-and-manipulation-of-errors</a> (the proposal/doc for swift’s current error handling) and John McCall had this to say about it:<div><br><blockquote type="cite"><div>We considered it, had some specifics worked out, and then decided to put it on hold. Part of our reasoning was that it seemed more like an implementation detail of the async / CPS-conversion features we’d like to provide than an independently valuable feature, given that we don’t want to encourage people to write library interfaces using functional-style error handling instead of throws.</div><div><br></div><div>It’s also a feature that’s directly affected by the design of typed throws, which in turn poses some usability challenges for it. For example, without typed throws you really just want the type to be Result<T>. With typed throws, can you still write that, or do you have to write Result<T, ErrorType>? Also, if we want every function result signature to have a corresponding Result<> type, does that permanently prevent us to supporting multiple error types with “typed throws”? Also, would it be too frustrating to work with typed Result values if we don’t allow implicit covariant conversions along one or both dimensions?</div></blockquote><br>(From <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001433.html" target="_blank">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001433.html</a>)</div></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>