wasm_thread icon indicating copy to clipboard operation
wasm_thread copied to clipboard

A rust `std::thread` replacement for wasm32 target

Results 13 wasm_thread issues
Sort by recently updated
recently updated
newest added

It seems as if this library no longer functions. Tested the following in Chrome + Safari. After integrating into my main application with no success, with the minimal usage of...

The current method of executing a future is by blocking the thread with `futures::executor::block_on`. However, this also blocks the JavaScript event loop, so JavaScript promises will never resolve and awaiting...

While #18 is being discussed, this PR addresses one point which is only about closing the worker after the wasm entry point call. This allows calling methods such as `request_animation_frame`,...

Async entry points would allow using async channels inside web worker threads. This feature would probably need a major rewrite as discussed in https://github.com/chemicstry/wasm_thread/issues/8

I wanted to understand how the changes in the refactor branch "broke" my code So I made a minimal reproduce of the bug as an example, also having more example...

It might be a permission issue, or something else, but I can't quite tell after about a week of working on this. This code works fine when I load the...

Currently it's not possible to send/receive messages to/from web workers because library overtakes `on_message` callbacks. It would be nice to somehow allow sending custom messages over API. It might also...

I haven't been able to find a path that would allow me to do that

Currently there is no way to execute tests with `build-std` flag, because `wasm-pack` does not pass this flag to `cargo build`. https://github.com/rustwasm/wasm-pack/pull/851

environment: * rustc 1.80.0-nightly (72fdf913c 2024-06-05) * cargo 1.80.0-nightly (34a6a87d8 2024-06-04) * wasm-pack 0.12.1 * nightly-x86_64-pc-windows-msvc No cross domain, use self-signed HTTPS; cargo.toml ``` toml [package] name = "simple" version...