Repository navigation
keep the magnitude of truncated integer digits in the Dfp string constructor - #342
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #342 +/- ##
============================================
+ Coverage 86.54% 87.22% +0.67%
+ Complexity 9787 91 -9696
============================================
Files 532 499 -33
Lines 35516 33533 -1983
Branches 6194 5853 -341
============================================
- Hits 30738 29249 -1489
+ Misses 3518 3164 -354
+ Partials 1260 1120 -140 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dfp(DfpField, String) copies at most getRadixDigits() * 4 + 1 significant digits into its scratch buffer and stops reading the input once that buffer is full. If no decimal point has been seen by then, the decimal position is taken from the number of digits stored rather than the number of integer digits in the string, so every digit past the precision is lost from the exponent as well as the mantissa. With the default 20-digit field, newDfp("123456789012345678901234567890") returns 1.2345678901234568e20 instead of roughly 1.23e29, and "1234567890123456789012345678.5" gives the same e20 value because its decimal point sits past the cut-off and is never reached. The result is a finite, plausible-looking number that is off by a factor of ten per excess digit, with nothing beyond FLAG_INEXACT to signal it. It shows up when comparing toDouble() of long decimal strings against Double.parseDouble: the two agree up to 21 digits and then diverge sharply. When the buffer fills before a decimal point, the constructor now counts the remaining integer digits up to the point and uses that as the decimal position, so the value is still rounded at the precision limit but keeps its exponent; this is separate from the exponent handling changed in #341. The new test in DfpTest fails on master with
x = 1.2345678901234568e20and passes with the patch, andmvn verifyon commons-math-core, commons-math-legacy-exception and commons-math-legacy-core is clean, as are the Dfp-using tests in commons-math-legacy.