Stream: git-wasmtime

Topic: wasmtime / Issue #1672 Upstreaming and/or mentioning wasm...


view this post on Zulip Wasmtime GitHub notifications bot (May 08 2020 at 14:23):

Ekleog opened Issue #1672:

Hello,

I've just finished polishing wasmtime-async, a crate designed to make it easy to run wasm code interleaved with rust async code.

So I wanted to mention it here, so you know that I've done that :) And I also wondered whether you might be interested in upstreaming its contents, and/or mentioning it somewhere in wasmtime's docs, to make it more discoverable.

Anyway, I mostly wanted to submit that to show you some thanks for having done wasmtime!

Have a nice day,
Leo

view this post on Zulip Wasmtime GitHub notifications bot (May 14 2020 at 00:05):

sunfishcode commented on Issue #1672:

Thanks for submitting this! While I read in the docs that this is aimed at calling wasm code which does little but call async host code, for Wasmtime itself I expect we also want to consider use cases that let the runtime and WASI implementations integrate with the async mechanism, which looks like it would be hard to do with this approach. That said, this is an interesting point in the design space that I expect works well for the kinds of use cases described in the docs :-).

view this post on Zulip Wasmtime GitHub notifications bot (May 14 2020 at 20:06):

Ekleog commented on Issue #1672:

The world you describe would be even greater indeed! Though it looks to me as though WASI is currently not designed in a way that permits async code to exist… but maybe there are plans to change that? :)

view this post on Zulip Wasmtime GitHub notifications bot (Nov 11 2020 at 19:57):

alexcrichton commented on Issue #1672:

I've opened https://github.com/bytecodealliance/rfcs/pull/2 for what it might look like supporting this in wasmtime itself, curious to hear what others think!


Last updated: Dec 23 2024 at 12:05 UTC