WebAssembly / WebAssembly/binaryen
wasm2asm: Needs support for exported tables
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
Right now if a table is exported from a wasm module no bindings for that are generated with wasm2asm, meaning that code which otherwise expects the wasm table to be there (to invoke wasm functions dynamically) won't work.
I think this'll probably want similar treatment to exporting memory where a shim object is injected with a wasm-table-like API to get the bare bones working.
cc @fitzgen
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 at the wasm2asm export-handling entry point and compare how exported memory is handled, since the issue suggests similar treatment for tables. Verify how a wasm module with an exported table is converted and ensure generated bindings expose a wasm-table-like API that supports dynamic wasm function invocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100