| 07:25 | <Jesse> | it sounds like there's no optimal time for the next call. The options I can see are:
Can you use an emoji to vote on this? There are emojis for numbers. You can vote for multiple options. A vote indicates that you're OK with the choice. |
| 07:59 | <sffc> | We didn't get around to fully discussing Rationals at the TG2 meeting, so I don't have a lot of updates on that front. I think the main thing for Amount is making a better case that we benefit from a new prototype for it rather than "just a protocol". |
| 08:23 | <sffc> | On Decimal itself, I should note that we still haven't fully discussed https://github.com/tc39/proposal-decimal/issues/181. Issues like that ought to have champion group consensus before asking for Stage 2. |
| 08:25 | <sffc> | I feel uncomfortable that there are 62 open issues on the repository. They should be at least triaged into broad categories like "blocks stage 2", "blocks stage 2.7/3", and "nice-to-have for later" |
| 08:29 | <sffc> | I want to hear a compelling case for "why we can't just have a Math.decimalAdd function" with behavior as described in that issue. I claim that the only real reasons are ergonomics and the ability to represent more than 15 significant digits; in other words, nothing intrinsic about Decimal128. If that's true, fine, but let's be clear about it. And, assuming ergonomics are indeed the motivating factor, then an ergonomic Amount (with its own prototype) follows naturally. |
| 17:31 | <sffc> | ^ I guess what I'm trying to say is that, as champions, we should form consensus on the roadmap to Stage 2, including key issues to resolve and questions to answer. There was a small amount of backchannel discussion here and in Seattle, but we should turn that into action. Triaging issues into milestones is a great first step. |