This sounds really promising, especially with JSPI becoming more widespread (in emscripten we also have ASYNCIFY which be substituted for JSPI too, in most cases).
I don't know much about Rust or Tokio myself, so I cannot offer much guidance, but wonder if it would be good idea (once its ready) to add some basic tests to emscripten test suite (like we have for Rust itself), to make sure don't break this support as we evolve emscripten? cheers, sam On Tue, Jun 9, 2026 at 10:04 AM 'Guy Bedford' via emscripten-discuss < [email protected]> wrote: > Hi all, > > We recently landed support for the Emscripten target in the wasm-bindgen > project and are exploring its adoption more widely for its benefits over > the wasm32-unknown-unknown platform agnostic target, in allowing better > libc compatibility. > > In the Rust ecosystem, Tokio is an async runtime that supports various > targets including only the WASI targets for Wasm, but it does not yet have > full support for the Emscripten Wasm target. > > This means that when building Rust projects for the Emscripten target, > applications using Tokio async features will likely not build correctly. > > There are perhaps two main runtime variations that can work for Emscripten > on Tokio here - a "hosted event loop" single-threaded runtime, with or > without a JSPI switch, and a comprehensive multi-threaded runtime. > > I have been fleshing out the first and simplest single-threaded hosted > event loop model in > https://gist.github.com/guybedford/9f534c70dd4b450294bf27eed139153f, and > also have a draft Emscripten prototype that is able to get the test suite > including many of the net tests passing. > > Towards a formal PR I have opened an initial discussion issue on the Tokio > repo in https://github.com/tokio-rs/tokio/issues/8194. > > The Tokio maintainers seem open to this Emscripten target support, under > the condition that there are clear maintainers for this target in Tokio. > Currently myself, Hood Chatham and Ingvar Stepanyan would be able to take > on this role. > > I'm sharing this topic for any further feedback from the Emscripten > maintainers and community on the design here and also to seek further > collaborators that may be interested in reviewing and assisting with the > maintenance of this target work, either formally or informally. > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/emscripten-discuss/eee88b87-565b-463e-a473-02b2a6a0420an%40googlegroups.com > <https://groups.google.com/d/msgid/emscripten-discuss/eee88b87-565b-463e-a473-02b2a6a0420an%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/emscripten-discuss/CAL_va2-WshTBM%3DJgRDr%2Bh_8n2yGFMxqUfzvyRGCuEL29TitBmQ%40mail.gmail.com.
