* [ruby-core:100611] [Ruby master Bug#9595] Float#to_d inconsistent between 2.0.0 and 2.1.1
[not found] <redmine.issue-9595.20140305162230.52@ruby-lang.org>
@ 2020-10-27 21:32 ` merch-redmine
0 siblings, 0 replies; only message in thread
From: merch-redmine @ 2020-10-27 21:32 UTC (permalink / raw)
To: ruby-core
Issue #9595 has been updated by jeremyevans0 (Jeremy Evans).
Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN)
Status changed from Assigned to Rejected
BigDecimal behavior has remained the same since 2.1, and 2.0's excessive precision was actually a bug, fixed in commit:1699396fe502d929ced019dc0dd3463a35fbf6d3.
----------------------------------------
Bug #9595: Float#to_d inconsistent between 2.0.0 and 2.1.1
https://bugs.ruby-lang.org/issues/9595#change-88242
* Author: boone (Mike Boone)
* Status: Rejected
* Priority: Normal
* Assignee: mrkn (Kenta Murata)
* ruby -v: ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-darwin13.0]
----------------------------------------
The following code produces different BigDecimal results in 2.0.0 vs. 2.1.1:
require 'big decimal'
require 'bigdecimal/util'
(1/1.3667).to_d
2.0.0 returns: #<BigDecimal:7fa7fc04dc28,'0.7316894709 885124E0',18(45)>
2.1.1 returns: #<BigDecimal:7fabd1a25768,'0.7316894709 88512E0',18(36)>
2.1.1 is a digit short. Related to #9305?
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-10-27 21:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <redmine.issue-9595.20140305162230.52@ruby-lang.org>
2020-10-27 21:32 ` [ruby-core:100611] [Ruby master Bug#9595] Float#to_d inconsistent between 2.0.0 and 2.1.1 merch-redmine
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).