Stream: git-wasmtime

Topic: wasmtime / issue #1603 Cannot virtualize WASI imports today

Wasmtime GitHub notifications bot (May 10 2024 at 02:23):

alexcrichton closed issue #1603:

This is an issue specific for this repository spawned from https://github.com/bytecodealliance/wasmtime-py/issues/2. Unfortunately it is not possible to virtualize WASI imports and functionality today where the virtualization may eventually delegate to the original implementations. The reason for this has to do with how the original module's linear memory makes its way to the wasi instance. Today this is done via the Caller structure, but this is brittle because once virtualized your Caller is different.

AFAIK we don't have a great answer for this today until we can figure out how to create a WASI instance with a memory or something like that.

Wasmtime GitHub notifications bot (May 10 2024 at 02:23):

alexcrichton commented on issue #1603:

This was a major design decision for the component model, so closing.

Last updated: Nov 22 2024 at 16:03 UTC