We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1_000_000_000.12345.to_d
I've found weird behavior in bigdecimal 3.0.1 when I was testing rails/rails#42125.
1_000_000_000.12345.to_d #=> 0.100000000012345e10 1.000_000_000_12345.to_d #=> 0.100000000012345e1
1_000_000_000.12345.to_d #=> 0.1e10 1.000_000_000_12345.to_d #=> 0.1e1
The text was updated successfully, but these errors were encountered:
Thank you for the report. I couldn't remember the bugs including this are remaining in the master branch before releasing 3.0.1. 🤦
Sorry, something went wrong.
Add tests for the issue GH-192
eb77aaf
Fix trailing zeros handling in rb_uint64_convert_to_BigDecimal
f356fe8
Fix GH-192
e864828
eebc98b
mrkn
Successfully merging a pull request may close this issue.
I've found weird behavior in bigdecimal 3.0.1 when I was testing rails/rails#42125.
Expected behavior
Actual behavior
The text was updated successfully, but these errors were encountered: