21e0a99884
This commit deletes the old C implementation of the original `wasi_unstable` module, instead only leaving around our single `wasmtime-wasi` crate as the implementation for both `wasi_snapshot_preview1` and `wasi_unstable`. This hasn't been discussed (AFAIK) up until now, so this is also a proposal! Some thoughts in favor of this deletion I would have are: * This has been off-by-default for ages * We don't build or test any of this on CI * Published binaries with `wasmtime` do not have this possibility enabled * Future refactorings to the `wasmtime-wasi` crate will either need to work around how the C implementation is different or bring it up to speed. This is motivated by the last bullet point where I was working on getting `wasmtime-wasi` working purely as an implementation detail on top of the `wasmtime` crate itself, but quickly ran into a case where the CLI would need to multiplex all sorts of wasi implementations. In any case I'm curious what others think, is this too soon? Is there something remaining blocking this? (etc)
Wasmtime: a WebAssembly Runtime
A Bytecode Alliance project
Wasmtime is a standalone wasm-only optimizing runtime for WebAssembly and WASI. It runs WebAssembly code outside of the Web, and can be used both as a command-line utility or as a library embedded in a larger application.
To get started, visit wasmtime.dev.
There are Rust, C, and C++ toolchains that can compile programs with WASI. See the WASI intro for more information, and the WASI tutorial for a tutorial on compiling and running programs using WASI and wasmtime, as well as an overview of the filesystem sandboxing system.
Wasmtime passes the WebAssembly spec testsuite. To run it, update the
tests/spec_testsuite submodule with git submodule update --remote, and it
will be run as part of cargo test.
Wasmtime does not yet implement Spectre mitigations, however this is a subject of ongoing research.
Additional goals for Wasmtime include:
- Support a variety of host APIs (not just WASI), with fast calling sequences, and develop proposals for additional API modules to be part of WASI.
- Facilitate development and testing around the Cranelift and Lightbeam JITs, and other WebAssembly execution strategies.
- Develop a native ABI used for compiling WebAssembly suitable for use in both JIT and AOT to native object files.
Including Wasmtime in your project
Wasmtime exposes an API for embedding as a library through the wasmtime subcrate,
which contains both a high-level and safe Rust API, as well as a C-compatible API
compatible with the proposed WebAssembly C API.
For more information, see the Rust API embedding chapter of the Wasmtime documentation.
It's Wasmtime.