Open question: How to deal errors

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, rust
Domain
api

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.

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.

Dominant language
Rust
Stars
220
Forks
15
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/wasi-webgpu

All issues in WebAssembly/wasi-webgpu

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.