torvyn-engine
Wasm engine abstraction and component invocation layer for the Torvyn reactive streaming runtime.
This crate provides:
- [
WasmEngine] — abstract interface for Wasm runtime operations (compile, instantiate, fuel/memory management). - [
ComponentInvoker] — the hot-path typed invocation interface between the reactor and Wasm execution (Gap G-01 fix). - [
WasmtimeEngine] — Wasmtime-basedWasmEngineimplementation (feature:wasmtime-backend). - [
WasmtimeInvoker] — Wasmtime-basedComponentInvokerimplementation (feature:wasmtime-backend). - [
CompiledComponentCache] — compiled component cache with disk support. - Mock implementations for testing downstream crates (feature:
mock).
Feature Flags
wasmtime-backend(default) — enables the Wasmtime backend.mock— enables mock implementations for testing.tracing-support— enables structured logging via thetracingcrate.
Architecture
Per Doc 02, Section 3: all Wasm engine interactions go through the
WasmEngine trait to insulate Torvyn from Wasmtime-specific APIs.
The ComponentInvoker trait (Doc 10, Gap G-01) provides typed
hot-path invocation between the reactor and Wasm execution.