cranelift

rust jit wasm webassembly runtime wasi cranelift sandbox wasmtime

Alex Crichton 7b311004b5 Leverage Cargo's workspace inheritance feature (#4905 ) * Leverage Cargo's workspace inheritance feature This commit is an attempt to reduce the complexity of the Cargo manifests in this repository with Cargo's workspace-inheritance feature becoming stable in Rust 1.64.0. This feature allows specifying fields in the root workspace `Cargo.toml` which are then reused throughout the workspace. For example this PR shares definitions such as: * All of the Wasmtime-family of crates now use `version.workspace = true` to have a single location which defines the version number. * All crates use `edition.workspace = true` to have one default edition for the entire workspace. * Common dependencies are listed in `[workspace.dependencies]` to avoid typing the same version number in a lot of different places (e.g. the `wasmparser = "0.89.0"` is now in just one spot. Currently the workspace-inheritance feature doesn't allow having two different versions to inherit, so all of the Cranelift-family of crates still manually specify their version. The inter-crate dependencies, however, are shared amongst the root workspace. This feature can be seen as a method of "preprocessing" of sorts for Cargo manifests. This will help us develop Wasmtime but shouldn't have any actual impact on the published artifacts -- everything's dependency lists are still the same. * Fix wasi-crypto tests		2 years ago
..
src	Reorganize wasi-misc-tests. (#575)	5 years ago
tests/wasm_tests	feat: rely on `tracing-subscriber` in tests (#4950)	2 years ago
wasi-tests	Leverage Cargo's workspace inheritance feature (#4905)	2 years ago
Cargo.toml	Leverage Cargo's workspace inheritance feature (#4905)	2 years ago
README.md	Don't implicitly create empty files in VirtualDir::openat (#2235)	4 years ago
build.rs	Remove dependency on `more-asserts` (#4408)	2 years ago

README.md

This is the test-programs crate, which builds and runs whole programs compiled to wasm32-wasi.

To actually run these tests, the test-programs feature must be enabled, e.g.:

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