bytecodealliance / bytecodealliance/ComponentizeJS
variant errors on top-level errors mask real error
- Dominant language
- Rust
- Stars
- 391
- Forks
- 53
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 1
Description
When using say a restricted error variant, throwing an unsupported error will be masked by the "invalid variant" error in the bindings.
In componentize bindings, we should specially handle invalid error variants at the top-level to be able to provide better debugging output.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the componentize bindings path that handles restricted error variants, focusing on how an unsupported top-level error becomes an invalid-variant error. Reproduce the masking behavior and compare the available error information. Done means the original unsupported error remains visible in the debugging output instead of being masked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100