Inconsistency between Bigdecimal 3.0.x and 3.1.x about bigdecimal HOT 4 CLOSED

I don't have a fix for this, but I can confirm this does happen to me as well. We are trying to update from Ruby 2.7 to 3.1 and we had tests fail due to an unexpected increase in precision that was previously not there. Dropping to 3.0.2 gets the results back to what we expect.

from bigdecimal.

@thorstenspringhart BigDecimal does not preserve the result precision of BigDecimal#/ among the different versions. In recent change, we increased the result precision of BigDecimal#/ for the case of infinite decimals. If you need to control the precision of division, you must use BigDecimal#div instead of BigDecimal#/.

from bigdecimal.

Could you please describe more detailed information? I cannot investigate the issue you encountered because I don't know what are other_budget, amounts_lines, and ratio_base.

from bigdecimal.

We have the same issue with a simple unit conversion:

Before the upgrade we had the following result:

0> value = BigDecimal('64')
=> 0.64e2
0> result = (value -32)* 5 /9 +273.15
=> 0.290927777777777777778e3
0> result.to_s
=> "290.927777777777777778"

After the upgrade

0> value = BigDecimal('64')
=> 0.64e2
0> result = (value -32)* 5 /9 +273.15
=> 0.290927777777777777777777777777777777778e3
0> result.to_s
=> "290.927777777777777777777777777777777778"

from bigdecimal.