Issue #15987 has been updated by nobu (Nobuyoshi Nakada). Note: The rdoc of Kernel#Integer says: > Passing `nil` raises a TypeError, while passing a String that > does not conform with numeric representation raises an ArgumentError. and states: > This behavior can be altered by passing `exception: false`, > in this case a not convertible value will return `nil`. So the current behavior is as documented, at least. And this seems coming from `IO#read_nonblock` and so on. ---------------------------------------- Bug #15987: Let `exception` option in `Kernel#Complex`, `Kernel#Float`, `Kernel#Integer`, `Kernel#Rational` be falsy vs. truthy https://bugs.ruby-lang.org/issues/15987#change-79286 * Author: sawa (Tsuyoshi Sawada) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- The `exception` option in `Kernel#Complex`, `Kernel#Float`, `Kernel#Integer`, and `Kernel#Rational` distinguishes `false` vs. other values. ```ruby Integer("z", exception: false) #=> nil Integer("z", exception: nil) #>> ArgumentError: invalid value for Integer(): "z") ``` But in most other cases where a boolean notion is concerned (for example, the `chomp` option in `Kernel#gets`), the distinction is between falsy vs. truthy values. I request the distinction to be falsy vs. truthy. In other words, I would like the value `nil` to work on the falsy side rather than the truthy side like this. ```ruby Integer("z", exception: false) #=> nil Integer("z", exception: nil) #=> nil ``` -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>