-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Remove redundant Precision combination code in favor of Precision::min/max/add
#15659
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
Conversation
0f10878 to
d818b17
Compare
|
|
||
| /// If the given value is numerically greater than the original maximum value, | ||
| /// return the new maximum value with appropriate exactness information. | ||
| fn set_max_if_greater( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this code is the same as Precision::min and Precision::max, so we can avoid the duplication
d818b17 to
ef8b5ea
Compare
ef8b5ea to
7ac2c7a
Compare
Precision combination code in favor of Precision::min/max/add
xudong963
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @alamb
jayzhan211
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻
|
Thanks @xudong963 and @jayzhan211 |
Which issue does this PR close?
Precision::maxandset_max_if_greatermethods #15615Rationale for this change
We are trying to improve statistics handling (so we can use it more). It turns out that the code to aggregate statistics in ListingTable was repliated with code already present in Precision
What changes are included in this PR?
Are these changes tested?
By existing CI
Are there any user-facing changes?