-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
wasm-sdk: use wasmtime.Linker for resolving imports, only have one wa…
…smtime.Engine instance per pool (#3764) * wasm-sdk: use wasmtime.Linker for resolving imports No functional change here, but this is easier to read and understand: anything the module needs, the linker will try to satisfy using the defined module/name entries ("env.memory", "env.opa_println", etc). * wasm-sdk: only use one *wasmtime.Engine instance This should bring us a little more in-line with the https://docs.rs/wasmtime/0.29.0/wasmtime/#example-architecture > When the server starts, we’ll start off by creating an Engine (and > maybe tweaking Config settings if necessary). This Engine will be > the only engine for the lifetime of the server itself. > Next, we can compile our WebAssembly. Signed-off-by: Stephan Renatus <[email protected]>
- Loading branch information
Showing
2 changed files
with
23 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters