<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Xiaodi Wu wrote:</div><div><br></div><blockquote type="cite"><div>I just assumed that the core team's vision was that this would be addressed by a domain-specific floating point `areSame(a: Self, b: Self) -> Bool { return (a == 0 && b == 0) || (a <=> b) == .same }`. This is a valid equivalence relation afaik.</div></blockquote><br><div>I guess so, but it's a different from what Dmitri gave here:</div><div><br></div><div><blockquote type="cite"></blockquote><blockquote type="cite"><blockquote type="cite"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">7. What, in fact, is the proposed total order for the stdlib's floating-point types?</span></font></blockquote><span style="background-color: rgba(255, 255, 255, 0);"><br>The IEEE 754 definition.<br><br><a dir="ltr" href="https://github.com/apple/swift/blob/f318fe853d7898246db24d501f1ddc03c9eb8651/stdlib/public/core/FloatingPoint.swift.gyb#L855" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="2">https://github.com/apple/swift/blob/f318fe853d7898246db24d501f1ddc03c9eb8651/stdlib/public/core/FloatingPoint.swift.gyb#L855</a></span></blockquote><br></div><div>— Pyry</div><div><br></div></body></html>