Update `cuda.core` developer guide
Open
Nobody has claimed this yet.
- #1316 by @Andy-Jost — closed without merging
cuda.core
documentation
P1
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
- Explain the build system change/expectation
- Explain a typical development cycle (pure Python -> Cython -> C++)
- Explain the steps for cythonization
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 with the cuda.core developer guide and review the closed linked pull request for existing context. Document the build-system expectations, the pure Python to Cython to C++ development cycle, and the steps for cythonization; done means all three topics are explained in the guide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100