Stream: git-wasmtime

Topic: wasmtime / PR #2917 only sync and tokio get to have WasiC...


view this post on Zulip Wasmtime GitHub notifications bot (May 20 2021 at 23:12):

pchickey edited PR #2917 from pch/wasmtime_wasi_reexport_mess to main.

view this post on Zulip Wasmtime GitHub notifications bot (May 20 2021 at 23:13):

pchickey edited PR #2917 from pch/wasmtime_wasi_reexport_mess to main:

wasi-common's WasiCtxBuilder was really only useful wasi_cap_std_sync and
wasi_tokio to implement their own Builder on top of. But even so, wasi_common::WasiCtxBuilder was barely better than just manipulating a WasiCtx directly. So now the sync and tokio builders do so directly.

wasmtime-wasi was re-exporting wasi-common::WasiCtxBuilder is 1. not useful and 2. shadow's the
re-export of the right one in sync::*.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (May 20 2021 at 23:13):

pchickey edited PR #2917 from pch/wasmtime_wasi_reexport_mess to main:

wasi-common's WasiCtxBuilder was really only useful wasi_cap_std_sync and wasi_tokio to implement their own Builder on top of. But even so, wasi_common::WasiCtxBuilder was barely better than just manipulating a WasiCtx directly. So now the sync and tokio builders do so directly.

wasmtime-wasi was re-exporting wasi-common::WasiCtxBuilder is 1. not useful and 2. shadow's the
re-export of the right one in sync::*.

<!--

Please ensure that the following steps are all taken care of before submitting
the PR.

Please ensure all communication adheres to the code of conduct.
-->

view this post on Zulip Wasmtime GitHub notifications bot (May 20 2021 at 23:13):

pchickey requested alexcrichton for a review on PR #2917.


Last updated: Nov 22 2024 at 16:03 UTC