Feature #7978: boolean to_i - Ruby master - Ruby Issue Tracking System

=begin The current behavior is the following: nil.to_i => 0 false.to_i NoMethodError: undefined method `to_i' for false:FalseClass true.to_i NoMethodError: undefined method `to_i' for true:TrueClass This does not look very consistent to me. I think it could be useful to define (({false.to_i})) as 0 and (({true.to_i})) as 1. I think those are fairly common numeric values for False and True. These v

[kent-where-the-light-is]

nil has its role as a default value, true/false are not.