WebAssembly / WebAssembly/binaryen
Discussion: Binaryen Wasm Component
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
I haven't seen anything on this and was curious if anyone has attempted this or thought into this.
Currently, bindings to binaryen are exposed via the c and js api's, which both require separate maintenance. I know there have been some issues keeping the js api up to date in the past, and recently, the embind work, which aims to autogenerate the js api.
I am curious if anyone has taken a look at generating or creating a wit component interface for binaryen and then using the component in the current component model tooling to generate bindings for a language, as it would make binaryen extremely portable. Component model is still an early days proposal though, so I'm not sure if this would make sense to do now.
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
No files, tests, or implementation entry points are named. Start by reviewing Binaryen's existing c and js APIs, then investigate whether a wit component interface can integrate with current component model tooling to generate language bindings. Done would require a defined, agreed-upon implementation scope rather than an exploratory discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, javascript, wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100