Bug #11947: BigDecimal#coerce: unexpected behavior with Float

• Status: Closed
• Assignee: mrkn (Kenta Murata)
• Target version: -
• Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN

[lionel_perrin (Lionel PERRIN)]

I've noticed that:

BigDecimal('2') + 1   # => BigDecimal(3), OK
1 + BigDecimal('2')   # => BigDecimal(3), OK
# whereas
BigDecimal('2') + 1.1 # => BigDecimal(3.1), OK
1.1 + BigDecimal('2') # => Float(3.1), WHY?

I was expecting the latest to return a BigDecimal but it retuns a Float. In the unit tests for bigdecimal, one can find the following test:

assert_equal(2, 1 + BigDecimal.new("1"), '[ruby-core:25697]')

May be this behavior is required but I haven't found any reason for this.

Regards,

Lionel

[mrkn (Kenta Murata)]

• Status changed from Open to Assigned
• Assignee set to mrkn (Kenta Murata)

[mrkn (Kenta Murata)]

• Status changed from Assigned to Closed

This fixed on the current master branch of ruby/bigdecimal repository.
So I close this issue.