Files
pezkuwi-subxt/substrate/client/executor
Koute a7e3d819f8 Refactor sp-sandbox; make sure both sandbox executors are always tested (#10173)
* sp-sandbox: convert executors into normal `mod`s instead of using `include!`

* sp-sandbox: run `cargo fmt` on `host_executor.rs`

* sp-sandbox: abstract away the executors behind traits

* sp_sandbox: always compile both executors when possible

* sc-executor: make sure all sandbox tests run on both sandbox executors

* sc-executor: fix brainfart: actually call into the sandbox through the trait

* sc-runtime-test: fix cargo fmt

* sc-runtime-test: deduplicate executor-specific sandbox test entrypoints

* sc-executor: test each sandbox executor in a separate test

* cargo fmt (Github's conflict resolving thingy broke indentation)
2021-11-08 12:52:11 +00:00
..
2021-11-04 19:54:48 +01:00
2020-08-20 17:04:42 +02:00

A crate that provides means of executing/dispatching calls into the runtime.

There are a few responsibilities of this crate at the moment:

  • It provides an implementation of a common entrypoint for calling into the runtime, both wasm and compiled.
  • It defines the environment for the wasm execution, namely the host functions that are to be provided into the wasm runtime module.
  • It also provides the required infrastructure for executing the current wasm runtime (specified by the current value of :code in the provided externalities), i.e. interfacing with wasm engine used, instance cache.

License: GPL-3.0-or-later WITH Classpath-exception-2.0