From: tilo.sloboda@...
Date: 2020-07-14T19:56:49+00:00
Subject: [ruby-core:99170] [Ruby master Bug#17032] BigDecimal .to_d is behaving inconsistent compared to .to_f

Issue #17032 has been reported by TiloS (Tilo S).

----------------------------------------
Bug #17032: BigDecimal .to_d is behaving inconsistent compared to .to_f
https://bugs.ruby-lang.org/issues/17032

* Author: TiloS (Tilo S)
* Status: Open
* Priority: Normal
* ruby -v: 2.5.5
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------

As a Ruby user I would expect `.to_f` and `.to_d` to behave identically.

Specifically `nil.to_d` should behave like `nil.to_f`


2.5.5 :001 > require 'bigdecimal'
 => true
2.5.5 :002 > require 'bigdecimal/util'
 => true
2.5.5 :003 > nil.to_f
 => 0.0
2.5.5 :004 > nil.to_d
Traceback (most recent call last):
        2: from /Users/tsloboda/.rvm/rubies/ruby-2.5.5/bin/irb:11:in `<main>'
        1: from (irb):4
NoMethodError (undefined method `to_d' for nil:NilClass)

# users should not have to resort to this:

2.5.5 :005 > nil.to_f.to_d
 => 0.0



-- 
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>