You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Explicitly target WASI 0.2 compliance, with a migration path to WASI 0.3 for async.
Motivation
WASI standardizes the interface between WASM modules and host environments. Explicit compliance ensures Vera programs are portable across runtimes (wasmtime, wasmer, wazero). WASI 0.3 (release candidate in Wasmtime 37+, November 2025) adds native async with stream<T> and future<T> types that align with Vera's planned Async effect.
Current state
Vera currently uses ad-hoc host function imports for IO operations. These work with wasmtime but are not WASI-compliant.
Explicitly target WASI 0.2 compliance, with a migration path to WASI 0.3 for async.
Motivation
WASI standardizes the interface between WASM modules and host environments. Explicit compliance ensures Vera programs are portable across runtimes (wasmtime, wasmer, wazero). WASI 0.3 (release candidate in Wasmtime 37+, November 2025) adds native async with
stream<T>andfuture<T>types that align with Vera's planned Async effect.Current state
Vera currently uses ad-hoc host function imports for IO operations. These work with wasmtime but are not WASI-compliant.
Proposed work
Dependencies