Which is all fine and everything, until it starts spitting out decimal representations of integer values that aren't the actual integer value represented by a given float.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Literally, the bytes inside a JS interpreter's RAM will contain [43 d0 00 00 00 00 00 00], per the IEEE 754 spec that *means 4611686018427387904*, and yet you call toString on that value and it returns something else. I don't know how to make this any clearer.
Put another way: when given certain integer-valued floats and told to convert them to a string, JS is *returning a string that contains a different integer*. Sure it *rounds* to the same integer when converted to a float, but why muck it up?
-
-
That's like having a 50 dollar bill and saying I have a 53 dollar bill and claiming I'm right, because although a 53 dollar bill doesn't exist, the closest possible bill is a 50 dollar bill, which is what I have, so clearly it must be fine to say I have a 53 dollar bill.
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.