<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Then we are fundamentally at odds, because I am categorically opposed to any solution that does <i class="">not</i> have specific meaning attached to the two variants. Either is an awful type that only serves to make APIs harder to understand, and literally every non-trivial usage of Either I’ve actually seen in practice, it has been used exactly the way Result<T> would naturally be defined (where “trivial” means usage in any kind of actual API, as opposed to sample code or scratch functions using Either to prototype something that, if turned into actual API, would replace the usage of Either with a more well-defined enum). And the existence of Either only serves to encourage people to use it, which produces an overall negative effect on the quality of APIs.</div><div class=""><br class=""></div><div class="">-Kevin Ballard</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 25, 2016, at 10:27 PM, Developer <<a href="mailto:devteam.codafi@gmail.com" class="">devteam.codafi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">Are you opposed to the name or the semantics?</div><div class=""><br class=""></div><div class="">I will not accept a revision that reduces the level of abstraction of the current proposal. I will, however, accept name changes. Result, though, I believe is out of the question. It strongly implies a common but pointed set of semantics that discourage thinking of this type as data and more as an alternative to throws. I do not wish to emphasize the error case, or the theoretical case, I wish to encourage the general case. We must remember that despite Rust's success, they do not have to live alongside an exceptions mechanism like Either does.<br class=""><br class=""><div class="">~Robert Widmann</div></div><div class=""><br class="">2016/01/26 0:55、Kevin Ballard via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> のメッセージ:<br class=""><br class=""></div><blockquote type="cite" class=""><div class="">
<title class=""></title>
<div class="">There absolutely is a cost. `Result<T>` has a rather intuitive meaning. `Either<T>` has <i class="">no intuitive meaning whatsoever</i>. It says absolutely <i class="">nothing</i> about what it means beyond the fact that there are two potential values. As a result, it is a largely useless type whose sole redeeming feature is it allows developers to avoid having to define their own enum, but in most cases that aren't covered by Result<T> you actually <i class="">want</i> to define your own enum so you can attach meaning to the value.<br class=""></div>
<div class=""> </div>
<div class="">If it's not obvious, I'm very strongly against having a generic Either type, but I do want a Result<T> or Result<T,E>.<br class=""></div>
<div class=""> </div>
<div class="">-Kevin Ballard</div>
<div class=""> </div>
<div class="">On Fri, Jan 22, 2016, at 10:22 PM, Developer via swift-evolution wrote:<br class=""></div>
<blockquote type="cite" class=""><div class=""><div class="">My overwhelming concern, after having a conversation with Chris, is that implementing a Result<T> means we are strongly implying a particular semantics and use case when we could generalize and abstract for no cost but an extra generic parameter. In F#, Core.Choice can be used to build a Validation or Result monad, but the converse is impossible.<br class=""></div>
<div class=""> </div>
<div class="">~Robert Widmann<br class=""></div>
</div>
<div class=""><div class=""> </div>
<div class="">2016/01/23 1:05、Rob Mayoff via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> のメッセージ:<br class=""></div>
</div>
<blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex;" class=""><div class="">Just added a section of motivating examples to the Either proposal. Ping me if you have any more that I missed ('cause I'm sure I did miss a lot).<br class=""></div>
<div class=""> </div>
<div class=""> <a href="https://github.com/typelift/swift-evolution/blob/either-or/proposals/0024-either.md#motivating-examples" class="">https://github.com/typelift/swift-evolution/blob/either-or/proposals/0024-either.md#motivating-examples</a><br class=""></div>
<div class=""> </div>
</blockquote><div class=""> </div>
<div class="">Your motivating examples (including all the projects you linked except "Any many more") overwhelmingly use the Either (or similar type) to represent success/failure. I'm not sure there's a single example where the names Left and Right actually make sense in the problem domain. I'm not 100% sure about func alternate in Madness/Alternation.swift. It definitely uses Left/Right to mean Failure/Result, but I couldn't tell if it also uses them as something else. Which makes those names all the more maddening.<br class=""></div>
<div class=""> </div>
<div class="">I checked my company's largest Scala project, which is over 300,000 lines. We use Scala's Try/Success/Failure in dozens of places. We use Either/Left/Right once, in a thrown-together report-generating script, which would probably have been written in awk or perl if it didn't need to read binary log files. (The ability of IntelliJ to reliably find all uses of a class or method is not to be underestimated. Hint hint, team Xcode.)<br class=""></div>
<div class=""> </div>
<div class="">I think a Result/Success/Failure type is warranted, but I'm very skeptical about generic Either/Left/Right.<br class=""></div>
<div class=""> </div>
</div>
</div>
</div>
</div>
</blockquote><blockquote type="cite" class=""><div class=""><div class=""><span class="">_______________________________________________</span><br class=""></div>
<div class=""><span class="">swift-evolution mailing list</span><br class=""></div>
<div class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""></div>
<div class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div>
</div>
</blockquote><div class=""><u class="">_______________________________________________</u><br class=""></div>
<div class="">swift-evolution mailing list<br class=""></div>
<div class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""></div>
<div class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div>
</blockquote><div class=""> </div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></blockquote></div></div></blockquote></div><br class=""></body></html>