WebAssembly / WebAssembly/component-model
Add runtime instantiation to component model
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 1.4k
- Forks
- 130
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 15
Description
Is there anyone already working on a draft for adding runtime instantiation to the component model?
Runtime instantiation means that a component can dynamically instantiate another component given its binary representation, and then invoke them. This is needed to have something similar to exec, where the number of imported instances and even the module code itself is not statically predefined but evolves programmatically. Currently one could define a custom protocol between the runtime and a component to have a similar effect. Use cases are flexible reusing of modules, runtime generation or fetching of modules (network or from disk), and a small demo program you could think of is a wasm component shell or wac REPL that itself runs as wasm component.
A few links in Luke's answer here: https://github.com/WebAssembly/WASI/issues/763
Contributor guide
No contributing guide indexed for this repository
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 entry points are named. Start by reading the linked WASI issue and the two existing comments to understand the proposed runtime-instantiation design; done would require an agreed component-model specification change rather than an isolated implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100