wasm-micro-runtime
wasm-micro-runtime copied to clipboard
bytecodealliance
Component model support
WASI has moved to preview 2, which is based on the Component Model.
In a recent community presentation, it was briefly mentioned that the component model would be in WAMR's roadmap, but I wasn't able to find an issue or more written information about this topic. I suggest using this issue as a feature request and as a way to attach any existing links to plans and timelines for this topic.
technically, preview2 does not require component model. i agree it's nice to have component model though.
btw, to make component model useful, i suspect we need to align our import/export model to the standard semantics (cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/1353) because many of the current use cases of component model involves import/export heavily.
btw, to make component model useful, i suspect we need to align our import/export model to the standard semantics
Yes, need fully alignment firstly.
I'm extremely interested in preview 2 and component model support in wamr for our usage. Love to hear thinking on how to help this out with wamr.
@squillace I am not sure about that. But would you mind sharing your usage about preview2 and component model. Since all I've heard about it are kinds of concern, and you are the first one to stand for it.
+1 on interest in @squillace use case! happy to try to find ways to support via contribution here.
how does preview2 work without component model? How does it know whether it is 32bit wasm or 64bit wasm?
