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.
-
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.