-
Notifications
You must be signed in to change notification settings - Fork 915
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
Fix a leftover _has_nulls change from Nullate #10211
Conversation
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.
That's amazing. Good catch Devavret.
Don't forget to change the copyright.
One more small fix in default value of null_equality. This one should've broken because |
In few minutes you might find one more :) |
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.
Nice find
Codecov Report
@@ Coverage Diff @@
## branch-22.04 #10211 +/- ##
================================================
+ Coverage 10.42% 10.47% +0.05%
================================================
Files 119 122 +3
Lines 20603 20501 -102
================================================
Hits 2148 2148
+ Misses 18455 18353 -102
Continue to review full report at Codecov.
|
So I hit this kind of thing when introducing the nullate type. Actually one of the motivations for coming up with this name was due to many name-collisions with the existing |
Should I do that in this PR? |
There are over 40 places that |
@gpucibot merge |
There was one missed change from template param has_nulls to member Nullate _has_nulls. It worked because has_nulls resolved to pointer to the function
has_nulls(table_view)
which is always true and didn't break at runtime because the subsequent is_null has a built in nullmask check.