Hi,

Thanks for this excellent example. It works well.

I am not sure this is the right "forum" to ask, but please point me to alternatives. However, I have a question: The example loads the modules statically. I have a use case in mind where I dynamically load WASM modules - depending on a configuration - and there can be different type of module combinations, so it does not make much sense to combine all possible modules together into one big fat binary (e.g. security issues, updating individual modules, hot reloading of new module versions etc.). Nevertheless, the modules have standard interfaces, so one can assume that at runtime the interfaces do not change, but just the underlying implementation. Maybe to facilitate the understanding, one can compare it to a plugin system.

I just wonder how one would realize this using WASM components. For example, the Wasmtime documentation provides an example that loads dynamically a module. I would like to do the same, but with wasm-components to avoid all the laborious work of copying data into a shared memory, interpreting it, validating the correctness etc.

Thank you.

Best regards

When following this awesome write-up I ran into issues linking the Wasm library to the rust-consumer module with wasmlink.

To get wasmlink I cloned the wit-bindgen repo and followed the wasmlink README to build it. Specifically, I ran, cargo build -p wasmlink-cli, which resulted in output built to wit-bindgen/target/debug/wasmlink. I modified the first line of the rust-consumer Makefile to target this binary for wasmlink.

Then, I built (with make build) and tried to link the WASI library and run the rust-consumer with make link run. make link fails with:

[2021-12-27T17:44:56Z ERROR] failed to parse interface file `../cache.wit`
    
    Caused by:
        invalid character in identifier '_'
             --> ../cache.wit:4:5
              |
            4 |     runtime_error,
              |     ^
make: *** [Makefile:9: link] Error 1

The interface file was successfully used to build the Wasm library (rust_wasi_impl.wasm); however, wasmlink seems unable to use it. Is there a different way I should be building and running wasmlink?