-
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
Eliminate literal parameters to uvector::set_element_async and device_scalar::set_value #7563
Eliminate literal parameters to uvector::set_element_async and device_scalar::set_value #7563
Conversation
auto const in{4}; | ||
auto const out{1}; | ||
input->set_value(in); | ||
output->set_value(out); |
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.
why this change?
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 will not pass CI until rapidsai/rmm#725 is merged. |
rerun tests |
rerun tests |
@gpucibot merge |
Codecov Report
@@ Coverage Diff @@
## branch-0.19 #7563 +/- ##
===============================================
+ Coverage 81.86% 82.49% +0.62%
===============================================
Files 101 101
Lines 16884 17402 +518
===============================================
+ Hits 13822 14355 +533
+ Misses 3062 3047 -15
Continue to review full report at Codecov.
|
rerun tests |
After rapidsai/rmm#725 is merged, this PR updates cuspatial to eliminate passing literal values to
device_scalar::set_value
.Note there are still similar issues with uses of
cudf::scalar
that need to be addressed. But I wanted to get this open before the end of the week. This can be merged after RMM 725 is merged to fix the build, so I think thescalar
issues should be fixed separately.