<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Dmitri Gribenko wrote:</div><div><br></div><blockquote type="cite"><blockquote type="cite"><span>7. What, in fact, is the proposed total order for the stdlib's floating-point types?</span><div style="display: none;"><br></div></blockquote><span></span><br><span>The IEEE 754 definition.</span><br><span></span><br><span><a href="https://github.com/apple/swift/blob/f318fe853d7898246db24d501f1ddc03c9eb8651/stdlib/public/core/FloatingPoint.swift.gyb#L855">https://github.com/apple/swift/blob/f318fe853d7898246db24d501f1ddc03c9eb8651/stdlib/public/core/FloatingPoint.swift.gyb#L855</a></span></blockquote><br><div>Cool. So if I'm reading it correctly, that's exactly the same order as what I defined here, using bitPattern: <a href="http://swiftlang.ng.bluemix.net/#/repl/5791db33719d5d045b4d430c">http://swiftlang.ng.bluemix.net/#/repl/5791db33719d5d045b4d430c</a>. I suppose your implementation is better in the usual case where most values are in the range of -Double.infinity ... Double.infinity.</div><div><br></div><div>— Pyry</div><div><br></div></body></html>