Relax key/payload/slot type constraints to enable 1B and 2B types
Open
Nobody has claimed this yet.
good first issue
P2: Nice to have
type: improvement
- Dominant language
- Cuda
- Stars
- 667
- Forks
- 120
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 4
Description
I think we are too strict on the key/payload/slot type constraints.
cuda::atomic_refsupports 1B and 2B operations. This is is to be explored in a future PR.
Originally posted by @sleeepyjack in #803
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 reviewing the constraints discussed in PR #803 and the supported 1B and 2B operations in cuda::atomic_ref. Trace where key, payload, and slot type constraints are enforced, then define completion as allowing the supported 1B and 2B types without weakening unrelated constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100