Avoid private cudf DeviceScalar in favor of using pylibcudf & pyarrow #2090
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.
Description
In cudf, I'm looking to ultimately remove the
DeviceScalar
implementation in favor of usingpylibcudf.Scalar
andpyarrow
.Before, it appears there was a cudf helper from getting an element from a string column's child (offset) column. There now exists pylibcudf APIs to do this and therefore can avoid having to directly access DeviceScalar
By Submitting this PR I confirm: