WebAssembly / WebAssembly/WASI
"Get Started" for Compiler Authors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Hi! I'm a dev over on https://github.com/grain-lang/grain. Grain is a language that primary compiles to WebAssembly, and we want to start transitioning to become WASI-compliant.
We're mostly looking to know the bare minimum for us to get started—how WASI-compliant modules are loaded (how imports are handled, what export from a module is invoked on instantiation (if any)) and how wasm modules access WASI values (if functions/etc look like any other import, or if some wasm magic happens).
If there's any relevant documentation you could point us to, that'd be fantastic; otherwise it'd be greatly appreciated if you could give us a quick primer! 🙏🏽
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 the WASI specification and documentation relevant to module instantiation, imports, exports, and access to WASI values. Produce a concise primer or links that answer each question for compiler authors, with enough context for Grain to identify its next implementation steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100