Stream: git-wasmtime

Topic: wasmtime / issue #4541 Question: Rust non-multithreaded A...

Wasmtime GitHub notifications bot (Jul 27 2022 at 11:47):

Max-Meldrum opened issue #4541:

Hi!

It seems to me that many internal functions such as call_async or wrap_async have explicit requirements on Send + Sync. Is there any way of running wasmtime with a non-multithreaded runtime, or is it mainly supposed to integrate well with tokio?

Cheers

Wasmtime GitHub notifications bot (Jul 27 2022 at 15:19):

alexcrichton commented on issue #4541:

Currently, no, there's no support for futures without Send/Sync natively in the API. It may be possible with unsafe wrappers that document that it's not actually used in a Send/Sync context but short of that Wasmtime isn't well-built for this use case unfortunately.

Wasmtime GitHub notifications bot (Jul 28 2022 at 09:59):

Max-Meldrum commented on issue #4541:

Currently, no, there's no support for futures without Send/Sync natively in the API. It may be possible with unsafe wrappers that document that it's not actually used in a Send/Sync context but short of that Wasmtime isn't well-built for this use case unfortunately.

Thanks for the great answer.

Wasmtime GitHub notifications bot (Jul 28 2022 at 09:59):

Max-Meldrum closed issue #4541:

Hi!

It seems to me that many internal functions such as call_async or wrap_async have explicit requirements on Send + Sync. Is there any way of running wasmtime with a non-multithreaded runtime, or is it mainly supposed to integrate well with tokio?

Cheers

Last updated: Oct 23 2024 at 20:03 UTC