Jesse Alama

Right, the current intention is to model IEEE 754's `compare_total`AKA `totalCompare` as the default way to do comparisons, with `compare` available as a separate mode. ~~I'm not sure I understand...

The current status is that we'll have a Temporal-style `compare` operation that accepts arbitrary decimals, never throws, and whose range is { -1, 0, 1, NaN } (because of NaN...

The terminology is indeed regrettably sloppy. Thanks. I do mean "significand". I'll take a closer look at the spec and see if I can pick a disambiguating definition. At a...

I believe this has been taken care of now in the various iterations of feedback we've gone through in the last couple of months (mainly #161 and #158).

@scottfr Regarding the first point above, it seems like we could address your issue if we were to allow an "unlimited" option for specifying the number of decimal digits?

@Rudxain All good points. I was speaking imprecisely. I had only division in mind (that was the use case mentioned by @scottfr), and was tacitly thinking of cases where the...

> Wait, you may be onto something there. That's actually a good idea! (if implemented carefully). I think that what you mean is to tell the interpreter "hey, use as...

Just chiming in to this old issue: The current approach is (1). For users who know what they're doing, you can achieve (2) by converting a Number to a String...

> `1m/3m + 1m/3m + 1m/3m = // ?` > > What's the result here? It would be 0.99...999, with the number of 9s determined by some kind of context...

Thanks for spotting that. I took a look at the spec again. If I understand it correctly, we can compare quiet NaN (which is the only kind of NaN that...