Skip to content
This repository has been archived by the owner on May 11, 2020. It is now read-only.

Support WASI execution #116

Open
twitchyliquid64 opened this issue Mar 27, 2019 · 5 comments
Open

Support WASI execution #116

twitchyliquid64 opened this issue Mar 27, 2019 · 5 comments

Comments

@twitchyliquid64
Copy link
Contributor

Saw this on HN: https://hacks.mozilla.org/2019/03/standardizing-wasi-a-webassembly-system-interface/

We should consider implementing a package that exposes the WASI API.
@sbinet
Copy link
Contributor

sbinet commented Mar 28, 2019

yep, definitely.

@sbinet
Copy link
Contributor

sbinet commented Mar 28, 2019

something to look at, too:

@twitchyliquid64
Copy link
Contributor Author

I'm thinking of doing the following:

  • Making a new subpackage: github.com/go-interpreter/wagon/wasi
  • This package exposes a wasi.MakeHostEnvironment
  • You pass host.WASIResolver as the wasm.ResolveFunc in a call to wasm.ReadModule, which will load the specified module + resolve the WASI imports for you.

Thoughts?

@twitchyliquid64
Copy link
Contributor Author

This is also a relevant doc, which enumerates the API surface we need to provide to support WASI.

@sbinet
Copy link
Contributor

sbinet commented Apr 3, 2019

SGTM.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sbinet @twitchyliquid64