[Migrated] We should figure out how to use Naga's `"span"` feature (for `example-runner-wgpu`).
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Issue automatically imported from old repo: https://github.com/EmbarkStudios/rust-gpu/issues/1017
Old labels: t: enhancement,a: examples,a: debugging
Originally creatd by eddyb on 2023-03-23T08:15:03Z
AFAICT, if we set features = ["span"] for naga in examples/runners/wgpu/Cargo.toml, we'll get more information on e.g. validation failures (which would've been nice this entire time, alas I didn't realize).
EDIT: nevermind, I got confused, span is already enabled by default, it just doesn't seem to do anything useful for SPIR-V input into Naga.
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 examples/runners/wgpu/Cargo.toml and inspect how Naga's default span feature is configured. Investigate why span information is not useful for SPIR-V input, especially for validation failures; done means documenting or implementing a concrete way for example-runner-wgpu to expose useful diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100