J. S. Choi

I think I’ve settled pretty firmly on type-overloading a few select `Math` methods. I think this fulfills the goal of “maximal consistency with precedent”. I’ve [edited the explainer](https://github.com/tc39/proposal-bigint-math/blob/main/README.md#philosophy) with the...

@jakobkummerow: I think these are all reasonable concerns. As you suggest, this issue is partially a question of trade-offs and partially a question of personal perspective. It’s true that I...

I presented a [brief update presentation][] about this issue to the Committee at the October plenary today. I tried to emphasize the symmetric tradeoff between “developers memorizing a table of...

I think the committee would probably push back against adding a new global. They would probably rather add methods to `BigInt`. I will raise the possibility of using `BigInt.hypot`, `min`,...

After the TC39 meeting, I currently plan to extend `Math.min`, `max`, and `hypot` to accept mixed BigInts and Numbers, because comparing BigInts and Numbers is well defined. We can already...

Maybe we should match `Array.prototype.sort` and be stable on ordering. Actually…in order to really match `Array.prototype.sort`, we perhaps should make \ `min` return the *first* minimum (i.e., the first element...

@sarahghp, @michaelficarra, @ljharb: Yeah, I was sloppy. What I had originally meant was to propose to match `Array.prototype.sort` **using ` [1, 0].sort((a, b) => a < b) [ 0, 1...

@michaelficarra: Argh, sorry, I’m really sleep deprived right now. Yes. `a < b ? -1 : a > b ? 1 : 0` is what I meant. I did not...

Okay, now that I’ve paid back my sleep debt, I should be able to think about this more coherently. There are three valid **developer mental models** I see: a **reduce**...

Yes, I think the usefulness of `min` and `max` over mixed Numbers/BigInts is equivalent to the usefulness of comparing Numbers and BigInts with `