-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Make IRComparer consider nans to be less than non-nans. #6626
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
Does this need any "is in strict fp mode" check? |
All reactions
Sorry, something went wrong.
I don't believe so, no. I don't think we ever want to consider |
All reactions
Sorry, something went wrong.
Sorry, I just realized I forgot to actually use the updated target in the test... going to fix that now. |
All reactions
Sorry, something went wrong.
Failing test looks like a performance flake to me... what are your thoughts, @abadams? |
All reactions
Sorry, something went wrong.
Leaving this for someone else to merge or patch further. |
All reactions
Sorry, something went wrong.
Thanks for fixing this issue! Would it be possible to make a 13.0.5 release with this fix? |
All reactions
Sorry, something went wrong.
@apartridge - that would be possible, but my bandwidth is somewhat limited until mid-week next week. |
All reactions
Sorry, something went wrong.
steven-johnson
abadams
Successfully merging this pull request may close these issues.
select statement that contains NaN value always returns NaN
Our IRComparer's
compare_scalar
believed that all floating point values are totally ordered, which is not true. NaNs always compare false in ordering comparisons.Fixes #6624