Ideas from rust-cuda crate
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
For the past 3+ years, I’ve developed my own rust-cuda (https://github.com/juntyr/rust-cuda) crate with the following goals:
- support generic kernels (initially via a linker wrapper, now via macro-driven instantiation)
- write safe kernels that are safe to call
Perhaps some ideas could be useful as community work now seems to converge in this org :)
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 referenced rust-cuda crate and comparing its generic-kernel and safe-kernel goals with this repository. The issue names no files, tests, or entry points, and does not define a concrete change or completion condition; a maintainer would need to scope the work first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100