3 ms·
The argument is still the same, now the user facing aspect is hidden (I don't know the Ruby source code, but I would guess they just rewrote the external facing
by yladiz 9y ago
The argument is still the same, now the user facing aspect is hidden (I don't know the Ruby source code, but I would guess they just rewrote the external facing code so the user doesn't have to care about Bignum or Fixnum, and just care about a single Integer).
As to your second point, why not just move everything to Number then and if it needs a decimal point, treat it as a floating point value? I argued in the original post that there can't be that many applications that depend on the current implementation, and those that do purposefully can be rewritten.
Edit: Integer -> Number
- dragonwriter 9y ago> The argument is still the same, now the user facing aspect is hidden Well, the language has changed so that they are unified. The underlying implementation may use different representations at different sizes, and presumably CRuby still uses the same internal split that the language exposed externally, at least for now. > As to your second point, why not just move everything to Integer then? Because not all numbers are integers, so you still need JS's number type (limited range and precision reals) if you have arbitrary precision integers.