-
Notifications
You must be signed in to change notification settings - Fork 264
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
preview2 questions #503
Comments
My understanding is that the answer is no, since the component model types have canonical mappings to MVP wasm types, and so even though WASI modules conform to the requirements of the component model the are (or can be) simple MVP wasm module, and the output of wasi-sdk will still be normal/MVP wasm modules (at least for now). |
do you mean, a runtime can still choose to implement the canonical mappings, which is a static plain core wasm abi, directly w/o knowing component-model/interface-types? |
Yes that is my understanding. @sunfishcode can confirm perhaps? |
Yes. |
And to be sure, my "yes" here was in response to sbc100's question. The component model defines a canonical ABI which is a core-wasm ABI. If there are any further questions, please file new issues! |
will preview2 require a component-model aware runtime? (to me it looks like "yes")
if yes, will there be no way to use wasi without component-model?
asking because, for some use cases of wasi, component-model looks very heavy-weight to me.
(both of implementation cost and runtime cost)
The text was updated successfully, but these errors were encountered: