Skip to content
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

Add interface types support #75

Open
mfateev opened this issue Oct 13, 2019 · 2 comments
Open

Add interface types support #75

mfateev opened this issue Oct 13, 2019 · 2 comments
Assignees
Labels
🎉 enhancement New feature or request
Projects

Comments

@mfateev
Copy link

mfateev commented Oct 13, 2019

Thanks for proposing a new feature!

Motivation

I would like to embed Go wasm code. Currently Go comes with syscall/js bindings. Having them implemented in go-ext-wasm would allow easy communication with the hosted Go code.

Proposed solution

Implement API bindings to syscall/js.

Alternatives

The better alternative would be a native way to bind to the hosted Go process functions. Ideally allowing more complex argument types like structures.

@mfateev mfateev added the 🎉 enhancement New feature or request label Oct 13, 2019
@mfateev
Copy link
Author

mfateev commented Oct 13, 2019

It looksl ike interface types is the way to go: https://hacks.mozilla.org/2019/08/webassembly-interface-types/

@mfateev mfateev changed the title Add syscall/js bindings Add interface types support Oct 13, 2019
@Hywan Hywan self-assigned this Oct 14, 2019
@Hywan
Copy link
Contributor

Hywan commented Oct 14, 2019

WebAssembly Interface Types (WIT) has changed a lot since the Mozilla blog post. We are working on implementing it, see wasmerio/wasmer#787. I think it will drastically change the Wasm landscape.

@Hywan Hywan added this to 🌱 In progress in Kanban Dec 4, 2019
@Hywan Hywan moved this from 🌱 In progress to 📬 Backlog in Kanban Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎉 enhancement New feature or request
Projects
Kanban
  
📬 Backlog
Development

No branches or pull requests

2 participants