`cargo clippy` with spirv target
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Currently, most projects run cargo clippy on the CPU target and hope that it covers most gpu-specific code as well. But that will ignore all #[gpu-only] functions and entry points, not checking them at all. We should investigate a way we can run clippy with spirv targets. This may be better suited for cargo gpu, since cargo gpu clippy would work quite nicely.
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
The issue names no files, tests, or entry points. Start by reviewing how cargo clippy handles the CPU target and how cargo gpu represents SPIR-V targets; done means establishing a viable way to lint gpu-only functions and entry points, potentially through a cargo gpu clippy command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100