WebAssembly / WebAssembly/wasi-webgpu
Open question: Should end methods take ownership?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 220
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Both GPURenderPassEncoder and GPUComputePassEncoder have .end() methods, and they're not supposed to be used after calling end.
JS doesn't have an ownership model so there's no way to enforce that it's never used again on a type level, but since wit does have an ownership model should we make end take ownership?
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
Start by comparing the linked GPURenderPassEncoder and GPUComputePassEncoder documentation with the repository's WIT definitions and ownership rules. The issue is done when the ownership behavior has a decided design and the relevant interface definitions reflect that decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100