Skip to content

Support running initialization with a custom wasmtime::Linker #49

Description

@fitzgen

Right now, you can either turn WASI on or off.

But there is no reason a user of the builder API shouldn't be able to provide their own wasmtime::Linker that defines non-WASI things that the Wasm module can import and use during initialization, or provide just some of WASI, or a virtualized/fake WASI, etc.

This would involve adding a new method to the builder API (

pub struct Wizer {
,
impl Wizer {
) to configure the provided wasmtime::Linker and then using that linker instead of creating a new one over here:
let mut linker = wasmtime::Linker::new(store.engine());

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions