<div dir="ltr">Here's the link:<div><a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160718/025132.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160718/025132.html</a><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 27, 2016 at 11:21 AM, Chris Lattner via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Aug 26, 2016, at 6:01 PM, Kevin Ballard <<a href="mailto:kevin@sb.org">kevin@sb.org</a>> wrote:<br>
> This change is going to have a HUGE impact for me. I use this sort of comparison _all the time_ and find it incredibly useful, and have had literally zero bugs caused by this. Surely I can't be the only one who uses this. I am not looking forward to copying & pasting a reimplementation of the comparison functions into every single project I work on.<br>
<br>
</span>Hi Kevin,<br>
<br>
This fits into a more general idea of introducing a better “ordering” concept defined in terms of three way comparison results (less/equal/greater). This would then become the primitive that sort would be built on, and would allow deriving the user friendly operators like < and <=.<br>
<br>
There was a sketch of this posted to swift-evolution several weeks ago, but I don’t have a link offhand.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Chris<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</div></div></blockquote></div><br></div>