Jesse Alama

> This function makes `Decimal128` work with the `Intl.NumberFormat.prototype.format[Range][ToParts]` functions, but it doesn't retain the tailing zeros as the OP suggests: > > > One of the guiding examples is...

Thanks for letting us know about this! That all sounds great. I'll take a look into those links.

That sounds fine. I wasn't aware of that aspect of IEEE 754. FWIW the remainder operation that's in the NPM library that accompanies this proposal follows the [_General Decimal Arithmetic...

Looks like we have some consensus that Decimal (regardless of the BigDecimal vs. Decimal128 discussion) should allow representing and working with only finite values?

Based on feedback we've received at the TC39 plenary, I'd like to re-open this discussion a bit. In short, the feedback I've received questions our deviation from official IEEE 754....

> They’re observably different Numbers with Object.is. Interesting! That's a good catch. OK, then I need to cancel my line of argument that we may want to "follow precedent". Based...

Current thinking about these values (working here in with the Decimal128 data model): + Infinity (positive, negative) might be useful in some scenarios. + Same for minus zero. + Banish...

> Number includes these types only because they are required for IEEE floating point compliance. They should not be added to BigDecimal in my opinion. Does your thinking extend to...

> What's the status of the progress? When we can go to stage3? We're still at stage 1. Stage 2 is possible this year, but probably not stage 3.

I didn't know about this use of decimal numbers inside WebKit -- thanks for the tip!