J. S. Choi

I presented a [brief update presentation][] about this issue to the Committee at the October plenary today. I presented the four potential mental models we could go with: the two...

@jakobkummerow: Thank you for the excellent insights. Your point about trying to stick with decisions that have already been made is well taken! Though I think there are a few...

@jakobkummerow: Great find with that @littledan quote; thank you! That quote embodies a tension between avoiding accidental loss of precision due to interchangeability…and reusing the same operations (which is, in...

@syg: This is a great point. It might be specific to `floor`/`ceil`/`round`/`trunc`, right? Do you think it applies to `pow`, `abs`, `sign`, `min`, and `max`? Those are the five operations...

Yes, that is true. But avoiding precision loss is *also* a spectrum. @waldemarhorwat pointed out in the August plenary that there is precedent for opt-in truncation in `/`. It was...

I think I’ve settled pretty firmly on eschewing both “maximal interchangeability” and “maximal interoperability” in favor of “maximal consistency with precedent”. I’ve [edited the explainer](https://github.com/tc39/proposal-bigint-math/blob/main/README.md#philosophy) with the following: > ##...

> We should keep `sqrt` and `cbrt` for BigInts because we have `pow`. > > The truncation towards zero behavior is unsurprising (it matches `/`) and mathematically useful, both directly...

> > sqrt and cbrt are just inverses of the most common cases of pow. It would be as weird to have one and not the other > > That...

I presented a [brief update presentation][] about this issue to the Committee at the October plenary today. I didn’t get any strong pushback over the overall philosophy and vision, although...

For what it’s worth, I’m exploring adding F# computation expressions as a future proposal. I’ve been writing in a Gist about this idea: [ES “context blocks”](https://gist.github.com/js-choi/854ccbc34787c697ea1f8458d6a1d660). (Warning: It’s very early...