Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add support for unary negation operator #17560
base: branch-25.02
Are you sure you want to change the base?
Add support for unary negation operator #17560
Changes from 8 commits
1ffae0b
6c5290f
819b0c8
3068215
6d3e1cc
688d60a
9d5365d
8134e18
4798838
4cc1033
9910117
0b219fd
cef040c
67118a0
e8779dd
b4b4f39
b19eebe
fe6a01a
a6ed9ad
48f4a21
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I am confused by this implementation. I thought we didn't want to provide an implementation for unsigned data types?
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.
I think that needs to happen at the dispatch layer, not SFINAE on the device operator itself. For example, we're not constraining types in other operators:
We only use SFINAE in this file when the implementation differs by type -- not to allow/disallow types.
Can we remove the SFINAE and just have this?
Also related to https://github.com/rapidsai/cudf/pull/17560/files#r1878099060
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.
Let me post the compile error I got when I removed it.
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.
We need another test that unsigned types, timestamps, strings, and other complex types fail.