-
Notifications
You must be signed in to change notification settings - Fork 217
wit-bindgen support for wasm start #262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It is, though a lot of the discussion there reflects the uncertainty at the time about the relationship between a wasm module and the outside environment. Many of the questions now have answers in the component model. The conceptual interface to the outside world is a component interface. But there's also a conceptual inner core module which implements a lowered form of the component interface through an adapter layer, for now using the Canonical ABI. So for the start function: Unlike the discussion in WebAssembly/WASI#19, we now know that components are acyclic, so the outer component can use the start function for running So we'll need the Canonical ABI to define a core-module exported function that is called at the logical time when the component start function is called. The call will happen after the core module is initialized and its exports are available. We'll need to pick a name for this function, and the main task there is to simply pick something nicer than |
I'm going to close this for the same reasons as I mentioned in #263 (comment) |
@sunfishcode is the discussion in WebAssembly/WASI#19 relevant to this one?
The text was updated successfully, but these errors were encountered: