Files

Pat Hickey 0f5bdc6497 only wasi_cap_std_sync and wasi_tokio need to define WasiCtxBuilders (#2917 )

* wasmtime-wasi: re-exporting this WasiCtxBuilder was shadowing the right one

wasi-common's WasiCtxBuilder is really only useful wasi_cap_std_sync and
wasi_tokio to implement their own Builder on top of.

This re-export of wasi-common's is 1. not useful and 2. shadow's the
re-export of the right one in sync::*.

* wasi-common: eliminate WasiCtxBuilder, make the builder methods on WasiCtx instead

* delete wasi-common::WasiCtxBuilder altogether

just put those methods directly on &mut WasiCtx.

As a bonus, the sync and tokio WasiCtxBuilder::build functions
are no longer fallible!

* bench fixes

* more test fixes

2021-05-21 12:59:39 -05:00

cap-std-sync

only wasi_cap_std_sync and wasi_tokio need to define WasiCtxBuilders (#2917 )

2021-05-21 12:59:39 -05:00

src

only wasi_cap_std_sync and wasi_tokio need to define WasiCtxBuilders (#2917 )

2021-05-21 12:59:39 -05:00

tokio

only wasi_cap_std_sync and wasi_tokio need to define WasiCtxBuilders (#2917 )

2021-05-21 12:59:39 -05:00

WASI @ ef8c1a53fe

Update submodules

2021-02-18 14:45:20 -08:00

build.rs

theres the bug

2021-02-04 15:38:02 -08:00

Cargo.toml

Bump versions: Wasmtime to 0.26.0, Cranelift to 0.73.0.

2021-04-05 10:48:42 -07:00

LICENSE

Initial reorg.

2019-11-08 06:35:40 -08:00

README.md

wasi-common no longer contains code derived from cloudabi-utils

2021-01-29 13:28:13 -08:00

README.md

`wasi-common`

A Bytecode Alliance project

A library providing a common implementation of WASI hostcalls for re-use in any WASI-enabled runtime.

The wasi-common crate will ultimately serve as a library providing a common implementation of WASI hostcalls for re-use in any WASI (and potentially non-WASI) runtimes such as Wasmtime and Lucet.

The library is an adaption of lucet-wasi crate from the Lucet project, and it is currently based on 40ae1df git revision.

Please note that the library requires Rust compiler version at least 1.37.0.

Supported syscalls

*nix

In our *nix implementation, we currently support the entire WASI API with the exception of socket hostcalls:

sock_recv
sock_send
sock_shutdown

We expect these to be implemented when network access is standardised.

We also currently do not support the proc_raise hostcall, as it is expected to be dropped entirely from WASI.

Windows

In our Windows implementation, we currently support the minimal subset of WASI API which allows for running the very basic "Hello world!" style WASM apps. More coming shortly, so stay tuned!

Development hints

When testing the crate, you may want to enable and run full wasm32 integration testsuite. This requires wasm32-wasi target installed which can be done as follows using rustup

rustup target add wasm32-wasi

Now, you should be able to run the integration testsuite by running cargo test on the test-programs package with test-programs/test_programs feature enabled:

cargo test --features test-programs/test_programs --package test-programs