| LOW | deny.toml | 1 | # This template contains all of the possible sections and their default values |
| LOW | deny.toml | 21 | # `target_family = "unix"` configuration, that only having windows targets in |
| LOW | deny.toml | 41 | #exclude = [] |
| LOW | deny.toml | 61 | |
| LOW | deny.toml | 81 | # If this is true, then cargo deny will use the git executable to fetch advisory database. |
| LOW | deny.toml | 141 | # The package spec the clarification applies to |
| LOW | deny.toml | 161 | # If true, ignores workspace crates that aren't published, or are only |
| LOW | deny.toml | 181 | # The graph highlighting used when creating dotgraphs for crates |
| LOW | deny.toml | 201 | deny = [ |
| LOW | deny.toml | 221 | # "hyper-rustls", |
| LOW | deny.toml | 241 | skip-tree = [ |
| LOW | .config/nextest.toml | 1 | [profile.ci] |
| LOW | tests/c-wasi-tests/sock_send_to.c | 1 | #include <assert.h> |
| LOW | tests/integration/cli/tests/snapshot.rs | 841 | // Performs a longjmp of a stack that was recorded before the fork. |
| LOW | tests/integration/cli/tests/snapshot.rs | 961 | "../../../../wasmer-test-files/integration/wasm/example-spawn.wasm" |
| LOW | …libExample/DylibExample/DylibExample-Bridging-Header.h | 1 | #include "wasm.h" |
| LOW | …sts/integration/ios/DylibExample/DylibExample/calc.cpp | 1 | // |
| LOW | tests/integration/ios/DylibExample/DylibExample/calc.h | 1 | // |
| LOW | tests/lib/wast/src/wast.rs | 401 | // ret.push(' '); |
| LOW | tests/compilers/traps.rs | 361 | |
| LOW | tests/compilers/issues.rs | 341 | &Value::I64(num.count_ones() as i64), |
| LOW | tests/compilers/issues.rs | 461 | /// |
| LOW | tests/compilers/wast.rs | 1 | use ::wasmer::sys::Features; |
| LOW | tests/compilers/wasi.rs | 1 | use std::fs::File; |
| LOW | examples/platform_ios_headless.rs | 1 | //! Defining an engine in Wasmer is one of the fundamental steps. |
| LOW | examples/features.rs | 1 | //! WebAssembly is a living standard. Wasmer integrates some |
| LOW | examples/imports_exports.rs | 1 | //! A Wasm module can import and export entities, like functions, memories, globals and tables. |
| LOW | examples/imports_exports.rs | 61 | println!("Creating the imported global..."); |
| LOW | examples/wasi_pipes.rs | 1 | //! Piping to and from a WASI compiled WebAssembly module with Wasmer. |
| LOW | examples/compiler_cranelift.rs | 1 | //! A Wasm module can be compiled with multiple compilers. |
| LOW | examples/metering.rs | 1 | //! Wasmer will let you easily run Wasm module in a Rust host. |
| LOW | examples/metering.rs | 61 | // Now let's create our metering middleware. |
| LOW | examples/wasi_manual_setup.rs | 1 | //! Running a WASI compiled WebAssembly module with Wasmer. |
| LOW | examples/hello_world.rs | 1 | //! This is a simple example introducing the core concepts of the Wasmer API. |
| LOW | examples/imports_function_env_global.rs | 1 | //! A Wasm module can import entities, like functions, memories, |
| LOW | examples/imports_function_env_global.rs | 61 | // We create some shared data here, `Arc` is required because we may |
| LOW | examples/memory.rs | 1 | //! With Wasmer you'll be able to interact with guest module memory. |
| LOW | examples/memory.rs | 101 | |
| LOW | examples/exports_function.rs | 1 | //! A Wasm module can export entities, like functions, memories, |
| LOW | examples/exports_function.rs | 41 | // Let's compile the Wasm module. |
| LOW | examples/exports_function.rs | 61 | // |
| LOW | examples/exports_function.rs | 81 | // `Rets`, respectively for the parameters and the results. If |
| LOW | examples/instance.rs | 1 | //! Wasmer will let you easily run Wasm module in a Rust host. |
| LOW | examples/instance.rs | 41 | |
| LOW | examples/imports_function_env.rs | 1 | //! A Wasm module can import entities, like functions, memories, |
| LOW | examples/compiler_singlepass.rs | 1 | //! A Wasm module can be compiled with multiple compilers. |
| LOW | examples/engine_dylib.rs | 1 | //! Defining an engine in Wasmer is one of the fundamental steps. |
| LOW | examples/engine_dylib.rs | 61 | // Here we go. |
| LOW | examples/exports_global.rs | 1 | //! A Wasm module can export entities, like functions, memories, |
| LOW | examples/exports_global.rs | 41 | |
| LOW | examples/exports_memory.rs | 1 | //! A Wasm module can export entities, like functions, memories, |
| LOW | examples/errors.rs | 1 | //! A Wasm module can sometimes be invalid or trigger traps, and in those case we will get |
| LOW | examples/compiler_llvm.rs | 1 | //! A Wasm module can be compiled with multiple compilers. |
| LOW | examples/imports_global.rs | 1 | //! A Wasm module can import entities, like functions, memories, |
| LOW | examples/early_exit.rs | 1 | //! There are cases where you may want to interrupt this synchronous execution of the Wasm module |
| LOW | examples/wasi.rs | 1 | //! Running a WASI compiled WebAssembly module with Wasmer. |
| LOW | examples/imports_function.rs | 1 | //! A Wasm module can import entities, like functions, memories, |
| LOW | examples/engine_headless.rs | 1 | //! Defining an engine in Wasmer is one of the fundamental steps. |
| LOW | examples/engine_headless.rs | 21 | //! will be executed can be very constrained. For such particular |
| LOW | examples/engine_headless.rs | 101 | // Here we go. |
| 865 more matches not shown… |