Switch to cuda::std::span once available
Open
Nobody has claimed this yet.
P3: Backlog
type: feature request
- Dominant language
- Cuda
- Stars
- 667
- Forks
- 120
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 4
Description
Our hash function implementations currently make use of the following function signature:
template <typename Extent>
constexpr result_type __host__ __device__ compute_bytes(std::byte const* data, Extent size) const noexcept
We should switch to cuda::std::span instead of raw pointers, once rapidsai/rapids-cmake#399 is resolved.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the hash function implementations that use compute_bytes(std::byte const* data, Extent size), then check the status of rapidsai/rapids-cmake#399. Once cuda::std::span is available, update the affected signatures and verify that the existing hash behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100