-
Notifications
You must be signed in to change notification settings - Fork 297
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
Implement the Wasm component-model
proposal
#897
Comments
Note: component model is in Phase 1 (not 4): From what other browsers have inputted, I believe is unlikely to transition phase any time in the close horizon |
@syrusakbary Thank you for the correction. I fixed the typo to avoid confusion. I usually try to only implement phase 4+ proposals in Wasmi since that provides safety to avoid maintenance burden with changes to the spec as is common for early phase proposals. However, with the |
It is already possible to use the component model with wasmi (as long as no multi-memory is required, see #776) using the |
Is this still planned? I see its removed from readme as planned. |
It is not planned nor unplanned. There are just many Wasm proposals that also need to be implemented and that have higher priority right now. Furthermore, the Wasm The list of Wasm proposals that are planned to be implemented more eagerly is roughly the following:
I just removed the Though according to @juntyr it is already possible to somehow use Wasmi with the |
This is about adding support for the
component-model
Wasm proposal.The
component-model
Wasm proposal is still in early Phase 1 and thus stabilization cannot be expected to happen soon, however, the people working on the Wasm standard are extremely convinced that it is going to become the defacto standard for all future Wasm runtimes to be supported since it is a huge enabler for the multi-language interopt vision of Wasm.The text was updated successfully, but these errors were encountered: