From: eregontp@... Date: 2019-07-13T10:18:45+00:00 Subject: [ruby-core:93737] [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 Eregon (Benoit Daloze). This issue is closed, it's probably best to discuss on a new one for different ideas. sawa (Tsuyoshi Sawada) wrote: > but I do not think that is a big deal. IMHO it is a big deal, Integer() should return either an `Integer` or `nil`, but never `false` or any other kind of value. `nil` means "absence of value", `false` doesn't have the same meaning. I believe everyone understands the exception: keyword should be given some kind of boolean value, using the value for anything else than deciding whether to raise exceptions would be very surprising. ---------------------------------------- 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-79374 * Author: sawa (Tsuyoshi Sawada) * Status: Closed * 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: