What does it mean that Ruby's "Integer" class was unified (Fixnum and Bignum merged) in Ruby 2.4+, and what is the practical implication?
Correct! Well done.
Incorrect.
The correct answer is B) Small and large integers are now both represented by the single Integer class, with the VM transparently switching internal representations as numbers grow, so code checking "is_a?(Fixnum)" became obsolete and was deprecated
Correct Answer
Small and large integers are now both represented by the single Integer class, with the VM transparently switching internal representations as numbers grow, so code checking "is_a?(Fixnum)" became obsolete and was deprecated
Before the unification, small integers (Fixnum) and arbitrarily large integers (Bignum) were separate classes; merging them into Integer simplified the type hierarchy since the distinction was an implementation detail that confused type checks.