Question about testing `block_on` code with `wstd::test`

[tomasol]

I use block_on to run async code inside the synchronous exported functions to comply with generated bindings.
In my integration tests I want to

1. Run some async code
2. call the exported function
3. Run some more async code

I cannot use wstd::test as it triggers "cannot wstd::runtime::block_on inside an existing block_on!", so I use regular tests and wrap step 1 and 3 with block_on. Is there a better way?

[pchickey]

No, there is no better way to handle this at this time. Fundamentally, block_on can only be running in one place in the program, globally, because the call site of that block_on is the control stack on which all futures are polled. In order to implement nested block_on (or as tokio calls the rough equivelant, spawn_blocking) we would need a way to switch stacks, which webassembly does not have until either shared-everything-threads or stack-switching proposals are stabilized.

[tomasol]

Got it, thanks.