[FEA] Pairwise distances to support int64_t internally (and downcast as necessary).
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
While migrating the pairwise distance API from RAFT, we realized that it's still accepting mdspans w/ indexing type of uint32_t. In order to keep our public facing APIs consistent in the meantime, we're accepting mdspan with int64_t index type on the outer API layer for now and then constructing new mdspans with the uint32_t indexing type for the call to the pairwise distances underneath.
This is a short-term fix and we should revisit this sometime in the near(ish) future to support int64_t efficiently in the pairwise distances layer itself.
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 at the pairwise distances API and its underlying pairwise distances layer; inspect how the outer mdspans are converted from int64_t indexing to uint32_t. Done means the API accepts int64_t-indexed mdspans while the underlying call receives the required uint32_t-indexed views, with downcasting handled as necessary.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100