Stream: git-wasmtime

Topic: wasmtime / issue #8187 [wasi] Confusing that async linker...

Wasmtime GitHub notifications bot (Mar 20 2024 at 09:22):

rylev opened issue #8187:

When adding wasi or wasi-http support to a linker through the various add_to_linker functions, I was unaware that there was a sync module that offered the same functionality without requiring async instantiation. It is not obvious to me why the async flavor would be the default especially for wasi (one could argue that for wasi-http it does make sense for async to be the default). While it's more typing perhaps putting the async variant in its own module and requiring the user to explicitly select async or sync would make the API more intuitive.

Wasmtime GitHub notifications bot (Mar 28 2024 at 03:31):

alexcrichton closed issue #8187:

When adding wasi or wasi-http support to a linker through the various add_to_linker functions, I was unaware that there was a sync module that offered the same functionality without requiring async instantiation. It is not obvious to me why the async flavor would be the default especially for wasi (one could argue that for wasi-http it does make sense for async to be the default). While it's more typing perhaps putting the async variant in its own module and requiring the user to explicitly select async or sync would make the API more intuitive.

Last updated: Nov 22 2024 at 17:03 UTC