From: matz@... Date: 2019-07-11T07:30:42+00:00 Subject: [ruby-core:93672] [Ruby master Bug#15987] Let `exception` option in `Kernel#Complex`, `Kernel#Float`, `Kernel#Integer`, `Kernel#Rational` be falsy vs. truthy Issue #15987 has been updated by matz (Yukihiro Matsumoto). Backport set to 2.5: UNKNOWN, 2.6: UNKNOWN Tracker changed from Feature to Bug It's a bug. It should be fixed. Matz. ---------------------------------------- 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-79283 * 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: