wasm-futures-executor
wasm-futures-executor copied to clipboard
wngr
Executor for asynchronous task based on wasm web workers.
Since this is a 'futures-executor' it is understandable that Threadpool::spawn and Threadpool::spawn_ok execute futures. However when spawning multiple threads from an async function, the lifetime of everything that is moved...
The idea is that you want to run a future that is not Send, but the function that produces that future is Send. Let's see if this solves my problem...
Check for example for * [crossOriginIsolated](https://developer.mozilla.org/en-US/docs/Web/API/crossOriginIsolated) * support for threads via [wasm-feature-detect](https://github.com/GoogleChromeLabs/wasm-feature-detect) * Unsupported browser etc.
Hello there, I tried compiling your crate with a recent rust nightly, which ended up in compilation errors. I could fix them using `thread_local` instead of `JsStatic` (as per https://rustwasm.github.io/wasm-bindgen/reference/static-js-objects.html),...
