Wasmtime GitHub notifications bot (May 10 2024 at 02:24): Wasmtime GitHub notifications bot (May 10 2024 at 02:24):alexcrichton closed issue #1270:
Currently WASI support is provided by the
wasmtime-wasicrate. This feels like it's a bit too much of a speedbump to pull in an extra crate and configure it just right to get support for WASI. I think that we'll want more turnkey (or at least documented) support in thewasmtimecrate itself.I think what I'd propose personally is:
- Merge the
wasmtime-wasicrate intowasmtime, deletingwasmtime-wasi- Ensure everything WASI-related is documented in the API
- Add a book example of how to instantiate WASI and link it to a module
- Delegate further improvements to https://github.com/bytecodealliance/wasmtime/issues/727
With my idea we still wouldn't really have turnkey support, but it's at least all in one crate and will be documented better than it is today. I think https://github.com/bytecodealliance/wasmtime/issues/727 will be where we want to figure out truly what a turnkey solution looks like.
Wasmtime GitHub notifications bot (May 10 2024 at 02:24):alexcrichton commented on issue #1270:
Things have worked pretty well with the wasmtime-wasi crate, so I'm going to close this.
Last updated: Nov 22 2024 at 16:03 UTC