Files

Jakub Konka f47133b229 Allow different Handles to act as stdio (#1600 )

* Allow any type which implements Handle to act as stdio

There have been requests to allow more than just raw OS handles to
act as stdio in `wasi-common`. This commit makes this possible by
loosening the requirement of the `WasiCtxBuilder` to accept any
type `T: Handle + 'static` to act as any of the stdio handles.

A couple words about correctness of this approach. Currently, since
we only have a single `Handle` super-trait to represent all possible
WASI handle types (files, dirs, stdio, pipes, virtual, etc.), it
is possible to pass in any type to act as stdio which can be wrong.
However, I envision this being a problem only in the near(est) future
until we work out how to split `Handle` into several traits, each
representing a different type of WASI resource. In this particular
case, this would be a resource which would implement the interface
required for a handle to act as a stdio (with appropriate rights, etc.).

* Use OsFile in c-api

* Add some documention to the types exposed by this PR, and a few others

Signed-off-by: Jakub Konka <kubkon@jakubkonka.com>

* Add construction examples and missing docs for Handle trait

* Fix example on Windows

* Merge wasi_preview_builder into create_preview1_instance

Co-authored-by: Pat Hickey <pat@moreproductive.org>

2020-06-09 20:19:20 +02:00

src

Allow different Handles to act as stdio (#1600 )

2020-06-09 20:19:20 +02:00

WASI @ 2b027d91c2

latest wasi submodule has witx 0.8.5, required for the error_types iter

2020-04-06 13:39:29 -07:00

wig

Wasmtime 0.17.0 and Cranelift 0.64.0. (#1805 )

2020-06-02 18:51:59 -07:00

winx

Wasmtime 0.17.0 and Cranelift 0.64.0. (#1805 )

2020-06-02 18:51:59 -07:00

yanix

Wasmtime 0.17.0 and Cranelift 0.64.0. (#1805 )

2020-06-02 18:51:59 -07:00

build.rs

Move back to only one WASI submodule (#1434 )

2020-03-30 14:45:23 -05:00

Cargo.toml

temporarily use tracing from git

2020-06-03 10:54:34 -07:00

LICENSE

Initial reorg.

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

LICENSE.cloudabi-utils

Initial reorg.

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

README.md

Fixes for cargo publish (#1416 )

2020-03-26 20:31:12 -07: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

Third-Party Code

Significant parts of our hostcall implementations are derived from the C implementations in cloudabi-utils. See LICENSE.cloudabi-utils for license information.