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
cache: put WASM compilation behind the action cache
Compiling a module to machine code is cacheable work like any other, so
model it as a CompileModule action keyed by the module checksum, wazero
version, GOOS, and GOARCH instead of handing wazero a private directory
outside the cache's discipline.
The action cache gains tree-shaped outputs for tools that read and
write output directories: PutTree stores every file under a directory
as a named output blob in the CAS, and GetTree materializes them back.
Compiled machine code is materialized into exec/<action-hash>, which
wazero's compilation cache reads on start; like the rest of the cache,
exec trees are safe to delete because the authoritative bytes live in
the CAS.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MPgq3rwip76D554BktbqR4
0 commit comments