WebAssembly / WebAssembly/wasi-webgpu
Consider changing around the feature items
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 220
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Consider changing gpu-supported-features and wgsl-language-features to flags, and remove gpu-feature-name.
gpu-supported-features and wgsl-language-features are defined in the spec as setlike<DOMString>, which is essentially a bag of bools, so flags would work nice for them.
gpu-supported-features can also be changed to gpu-features to take the place of both gpu-supported-features and gpu-feature-name.
gpu-device-descriptor.required-features - which is the only place gpu-feature-name is used - is currently option<list<gpu-feature-name>> and could just be changed to option<gpu-features>
Contributor guide
No contributing guide indexed for this repository
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
Review the spec definitions for gpu-supported-features, wgsl-language-features, gpu-feature-name, and gpu-device-descriptor.required-features. Resolve whether these should become flags or gpu-features, then update the affected API consistently; done means the feature representation and required-features option no longer conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100