My point is that floats *are* Proper Integers: up to 53 bits they can represent every possible integer, and beyond that they can represent certain integers (but those integers, they represent exactly). JS is printing a *different* integer than what the float represents.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
But Python doesn't do either of those when converting to a string, it uses 1.000000000000001e+18. That's *both* natural *and* makes the loss of precision clear. A number without a decimal point is *not* obviously not actually a precise integer to non-tech people.
-
-
In JS, BigInt(1000000000000001000) == 1000000000000001024u so that's no different from Python anyway. This is all just about the default string conversion hiding a surprise behind what looks like a straight integer in JS.
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.