Robert, the gist is notably vague on this point, so I'm hoping you will clarify. Are you proposing that FloatingPoint will break with IEEE754 semantics? What will be the result of `Float.nan == Float.nan`?<br><br>(My guess at the sanest outcome is that areSame/Equivalent() and <=> will be totally ordered but FloatingPoint types will override == and the standard comparison operators to maintain IEEE754 semantics, yes?)<br><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 21, 2016 at 11:02 PM Dmitri Gribenko 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">Hi,<br>
<br>
On Thu, Jul 21, 2016 at 6:11 PM, Robert Widmann via swift-evolution<br>
<<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
> Hello Swift Community,<br>
><br>
> Harlan Haskins, Jaden Geller, and I have been working on a proposal to clean<br>
> up the semantics of ordering relations in the standard library.<br>
<br>
Great work!<br>
<br>
As a part of your implementation, are you planning to add <=><br>
overloads for tuples, like we do now for comparison operators? (See<br>
stdlib/public/core/Tuple.swift.gyb.)<br>
<br>
Dmitri<br>
<br>
--<br>
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>>*/<br>
_______________________________________________<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>