wasmex icon indicating copy to clipboard operation
wasmex copied to clipboard

Interface Types Status ?

Open sleipnir opened this issue 4 years ago • 4 comments
trafficstars

What is the status for interface types support?

sleipnir avatar Aug 18 '21 21:08 sleipnir

Hey @sleipnir wasmex currently has no special code to support interface types. It's theoretically possible to support interface types, since wasmer seems to have (dated?) support for it 👉 https://github.com/wasmerio/interface-types

It's not clear at this moment how an elixir-facing API would look like. I personally never played with interface types before, so I don't come with experience here :)

tessi avatar Sep 15 '21 12:09 tessi

I don't have that experience either, but it would definitely be more intuitive to deal with a high-level typed interface rather than just raw bytes

sleipnir avatar Sep 15 '21 12:09 sleipnir

I just visited the interface types RFC and it says:

This proposal is currently inactive, with work having moved on to the component-model repo

However, the Component Model RFC, so I guess we have to look there :)

I also looked over the fence at what wasmtime is doing, and they don't have interface type support too (although they used to have some suport), see their tracking GH issue.

It seems wit-bindgen is something we could look at for code generation. Maybe eventually fulfilling the dream of automatically generating Elixir typespecs and behaviours for WASM APIs from a .wtix file. 🤔 We have some way to go to be near that, but it's certainly something I'd love to see for wasmex.

tessi avatar Aug 04 '22 07:08 tessi

Wasmtime removed its support for interface types as I recall. Generating the elixir type and behavior specs would be a big thing to see.

sleipnir avatar Aug 04 '22 19:08 sleipnir

closing this for now in an attempt to clean up old issues. feel free to (re-) open an issue if things change

tessi avatar Oct 06 '22 16:10 tessi