eduardomourar edited PR #6878:
Within the wasmtime CLI, the current default behavior is to only inject the synchronous functions to linkers. This will add a flag called
--async
that will inject the asynchronous one instead.This is required in order to enable back the
wasi-http
module because it has been implemented only with async functions. Additionally, it will help the async support code path to be tested as async should be enabled by default in the future.
eduardomourar edited PR #6878:
~~Within the wasmtime CLI, the current default behavior is to only inject the synchronous functions to linkers. This will add a flag called
--async
that will inject the asynchronous one instead.This is required in order to enable back the
wasi-http
module because it has been implemented only with async functions. Additionally, it will help the async support code path to be tested as async should be enabled by default in the future. ~~This will enable back the
wasi-http
module within the wasmtime CLI. We will make the bindgen synchronous through the tokio executor available in wasmtime.
eduardomourar edited PR #6878:
Within the wasmtime CLI, the current default behavior is to only inject the synchronous functions to linkers. This will add a flag called--async
that will inject the asynchronous one instead.
This is required in order to enable back thewasi-http
module because it has been implemented only with async functions. Additionally, it will help the async support code path to be tested as async should be enabled by default in the future.This will enable back the
wasi-http
module within the wasmtime CLI. We will make the bindgen synchronous through the tokio executor available in wasmtime.
eduardomourar updated PR #6878.
Last updated: Nov 22 2024 at 16:03 UTC