Bug #13232
closed
Updated by nobu (Nobuyoshi Nakada) over 8 years ago
- Description updated (diff)
- Status changed from Open to Assigned
- Assignee set to mrkn (Kenta Murata)
Seems correct to me.
Updated by romuloceccon (Rômulo Ceccon) over 8 years ago
I didn't realize there was a repo for BigDecimal when opening this issue. May I repost it there as a pull request?
Updated by romuloceccon (Rômulo Ceccon) over 8 years ago
Any update on this one?
Should I look for more easily reproducible steps? What about opening a issue/PR?
Thanks.
Updated by mrkn (Kenta Murata) over 8 years ago
I'm sorry for my late response.
I'll import your by tomorrow.
Thanks a lot.
Updated by mrkn (Kenta Murata) over 8 years ago
- Status changed from Assigned to Closed
Applied in changeset r57951.
bigdecimal: version 1.3.2
Import bigdecimal version 1.3.2. The full commit log is here:
https://.com/ruby/bigdecimal/compare/v1.3.1...v1.3.2
This fixes [ruby-core:79603] [Bug ]
Updated by hrsht (Harshit Chopra) almost 8 years ago
Sorry if it is not the right place to ask this question, but is it possible to backport this fix in ruby 2.4 and 2.3 versions? This issue came to light for us when using ruby 2.4, as with 2.4 BigDecimal now throws an error when trying to initialize with an invalid string.
So for us, it would fail at times when trying to instantiate a BigDecimal object in ruby like:
BigDecimal.new(1.0e-12)
raising error of the form:
invalid value for BigDecimal(): ""
Updated by usa (Usaku NAKAMURA) almost 8 years ago
- Backport changed from 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN to 2.2: WONTFIX, 2.3: REQUIRED, 2.4: REQUIRED
Updated by nagachika (Tomoyuki Chikanaga) over 7 years ago
- Backport changed from 2.2: WONTFIX, 2.3: REQUIRED, 2.4: REQUIRED to 2.2: WONTFIX, 2.3: REQUIRED, 2.4: DONE
ruby_2_4 r62638 merged revision(s) 57597,57951.