fix: floating point comparison was inexact #4372
Merged
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.
Description
fixes: #4370
Switches the generated Java code to convert the
double
to aString
, and then using this to build theBigDecimal
. This results in an exactBigDecimal
for the comparison.Without this change a
double
of0.1
is converted to aBigDecimal
of0.1000000000000000055511151231257827021181583404541015625
, which is greater than0.1
, hence the bug.Testing done
Tests added.
Reviewer checklist