-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
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.0 . to BigDecimal) != 1.0 - e.g. equality isn't working correctly #8855
Comments
After #7883, the consistency of |
Jaroslav Tulach reports a new STANDUP for yesterday (2024-02-14): Progress: - meetings
Next Day: equality in Big_Decimal |
Jaroslav Tulach reports a new STANDUP for yesterday (2024-02-15): Progress: Feb 15 - 10 h Next Day: equality in Big_Decimal
|
Jaroslav Tulach reports a new STANDUP for yesterday (2024-02-16): Progress: - Explictly Both Comparators: #9070 (comment)
Next Day: testing & documenting equality in Big_Decimal |
Jaroslav Tulach reports a new STANDUP for the last Saturday (2024-02-17): Progress: -
Next Day: integrate equality in
|
Jaroslav Tulach reports a new STANDUP for yesterday (2024-02-19): Progress: - documenting & integrated
Next Day: Planning next big thing... |
The support for non-builtin number types (as introduced by #8779) doesn't work well with
==
. As result of that certain tests had to be disabled. This is a follow up issue that tracks further work on the reimplementation ofEqualsNode
.The initial idea:
Catch:
hash
code!The text was updated successfully, but these errors were encountered: