WebAssembly / WebAssembly/wasi-webgpu
Open question: How to deal errors
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 220
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
How should we deal with errors? JS errors have constructors, messages, etc.
Should we replicate that, or should we just use simple enums instead?
Don't think we need an answer right now, just putting it here to open the discussion.
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
No files, tests, or entry points are named; start by reviewing this issue's open question about JavaScript-style errors versus simple enums. Done would require a documented, agreed error-handling design rather than an implementation target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100