You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
waPC partially fulfills the need to transfer data beyond integers between host and guest across languages in wazero. Apex expands on this to provide cross-language serialization for complex data types on top of WaPC.
However, it seems clear that WebAssembly Interface Templates are likely to dominate the future of this problem space.
I searched to find a WIT host bind generator for wazero and it doesn't seem to exist yet.
I haven't yet seen any posts discussing WIT host bindings for wazero anywhere either.
So before I dedicate a weekend to scoping out the work to write my own, I'd like to ask:
Has anyone given this topic any thought? (assume yes)
Does everyone consider WIT support a long term necessity for wazero? (also assume yes)
Are there any technical reasons why wit-bingen might not be possible for wazero?
Are there any technical reasons why wit-bingen might be more difficult with wazero than other runtimes?
Has anyone begun work on this effort?
From other wasm hosts in go:
bytecodealliance/wasmtime-go#170
Work will eventually be done in this repository to support the component model and *.wit-based bindgen, but for now there are not current plans to execute on that.
The text was updated successfully, but these errors were encountered:
But in short, we have zero intention to add any code before standardized (phase 5 of Wasm standard) phase, and hence WIT or whatever component model-related stuff is completely out of scope for now. Regardless of the state, the "support for WIT" should be implemented out of scope rathat than having here.
Simply answer you question (but please come in Gophers slack if you continue):
Does everyone consider WIT support a long term necessity for wazero? (also assume yes)
No for now, given that it's phase (phase 1/2 is completely "PoC" state, and are not worth the maintenance).
Are there any technical reasons why wit-bingen might not be possible for wazero?
I don't think so unless there's any peculiarity related to Component model
Are there any technical reasons why wit-bingen might be more difficult with wazero than other runtimes?
waPC partially fulfills the need to transfer data beyond integers between host and guest across languages in wazero.
Apex expands on this to provide cross-language serialization for complex data types on top of WaPC.
However, it seems clear that WebAssembly Interface Templates are likely to dominate the future of this problem space.
I searched to find a WIT host bind generator for wazero and it doesn't seem to exist yet.
I haven't yet seen any posts discussing WIT host bindings for wazero anywhere either.
So before I dedicate a weekend to scoping out the work to write my own, I'd like to ask:
From other wasm hosts in go:
The text was updated successfully, but these errors were encountered: