Update .wit files to allow referencing between host and guest interfaces
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 875
- Forks
- 68
- Avg merge
- 9d 5h
- Merged PRs (30d)
- 1
Description
Currently, we use JsValueTransport to facilitate moving values between the rb-abi-host and rb-abi-guest. Since the introduction of this workaround in #18 (May 2022), the WIT format implemented features such as worlds and import/exports. If we update our .wit files to use these new features I think JsValueTransport would no longer needed because the host and guest .wit can reference each other.
Contributor guide
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 with packages/npm-packages/ruby-wasm-wasi/src/index.ts at the mentioned JsValueTransport implementation, then locate the current rb-abi-host and rb-abi-guest .wit files. Compare their definitions with WIT worlds and import/export support. Done means the host and guest interfaces can reference each other without the JsValueTransport workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, typescript, wasm
- Domain
- api, compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100