-
Notifications
You must be signed in to change notification settings - Fork 80
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
Works with wit-bindgen? #170
Comments
Not currently, no. Work will eventually be done in this repository to support the component model and |
I see. We have some ideas about using WASM to build a subsequent business code dynamic distribution platform. I think It is necessary to reuse some type and define how to transfer between guest and host code using raw number type. It is still in the early research stage, I am not particularly familiar with WASM too, but It seems that component model (and wit IDL) is the upcoming standard to define these things, right? If so, I think I can try to look into it after serval weeks and try help integrate it in wasmtime-go. I will read some document about WASM first recently, thanks for your help. |
Indeed the component model is generally the standard for this sort of thing. You might want to take a look at the |
I saw somewhere last year that wit-bindgen can be used together with wasmtime's golang binding, but when I just went to the wit bindgen repo, I found that after switching to the component model, the implementation of the host side handed over to each runtime.
For now, the origin Rust wasmtime crate supports it, but is it possible to use it in wasmtime-go?
The text was updated successfully, but these errors were encountered: