We should support a version of instantiate that will continue to allow us to recommend it as the preferred instantiation method one dynamic linking / multiple modules become more popular.
WebAssembly.instantiateGroup({a:Promise<Response>, b:Promise<Response>, otherImports:importObject})
With this, the module at urlA could import the foo export of the module at urlB by importing from "b" "foo".
Questions:
- Do we want to support cycles or just DAGs?
- Do we want to support the BufferSource overload?
- How does this interact with ES6 modules? (or does it?)
We should support a version of instantiate that will continue to allow us to recommend it as the preferred instantiation method one dynamic linking / multiple modules become more popular.
WebAssembly.instantiateGroup({a:Promise<Response>, b:Promise<Response>, otherImports:importObject})With this, the module at urlA could import the foo export of the module at urlB by importing from "b" "foo".
Questions: