Wrong. The largest int that can be represented exactly in a 64-bit IEEE 754 floating point format is 0x1.fffffffffffffp+1023, which is an exact 309-digit integer that doesn't fit in a tweet, but can be approximated as 1.7976931348623157e+308.
-
It's true we could have added many numeric types ages ago, but browser wars I shut down JS standardization after 1999 ES3. When we got it restarted via Firefox it took too long, with divided member effort due to Silverlight, Dart, PNaCl, to find the champions and get tc39 moving.
I think the value in promoting BigInt (for more than specialized use cases) is that it's a lot better-behaved than Number; Number works until it doesn't and then things break. But for that to happen the core APIs need to start accepting BigInt for anything with int semantics.
-
-
https://github.com/tc39/proposal-bigint#left-for-future-proposals … Compatibility/interop and security dragons lurk in simply extending existing methods to take BigInt as well as Number. Will save it for later.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.