jakobkummerow

Since @binji asked... I think it is generally unfortunate that when writing software, we so often have to choose either checks or performance. For V8's perspective in this particular case,...

@sunfishcode I never said that safety (of the overall system) was optional. I said that in C, requiring a (claimed) size to be passed along with every array in a...

> fortunately, we're not trying to provide watertight safety guarantees here. In what sense is that "fortunate"? The *title* of the whole issue is "Safety in the API". What, precisely,...

Those implementations look good, and really fast! I see this as confirmation of my earlier view that adding `BigInt.log2` (or `BigInt.bitCount`, where log2 == bitcount-1) would be useful (because engines...

Slow rollout of engines with BigInt support (still only [~90%](https://caniuse.com/bigint)! Who wants to leave 10% of their potential users out in the cold? That's millions of people!), combined with lack...

So to summarize what you just said: people won't be able to actually write `Math.abs(some_bigint)` for many years. You don't think that's a reason to prefer a different design, where...

(I think when you say "yulia" you mean @codehag .)

I approve of dropping all the functions that don't make sense for BigInts or have no known use cases. One could take this a bit further still: - `Math.pow` has...

Just keep in mind that lack of engagement might also mean that people (who all have limited time!) just don't care all that much about a handful of one-liners: ```javascript...

Taking a step back here, would someone be able to shed some light on anticipated use cases? If we imagine code like: ``` let max = Math.max(...mixed_bag_of_numbers_and_bigints); let min =...