Is it required that imports and exports have the same namespace and thus cannot have share names? One common pattern for worlds will likely be "proxies" that have the same imports as exports and which simply wrap the imports in some functionality and reexport them.
(this isn't a show stopped obviously, but does make things a little less nice)
https://github.com/WebAssembly/component-model/pull/164
tldr: it makes bindings generators significantly simpler
note that this restriction is being lifted for importing/exporting interfaces (e.g. the proxy case) where we'll have:
world foo {
import wasi:http/proxy
export wasi:http/proxy
}
which is already possible today with import a: wasi:http/proxy
and export b: wasi:http/proxy
Last updated: Nov 22 2024 at 16:03 UTC