mirror of
https://github.com/fluencelabs/wasm-bindgen
synced 2025-04-03 19:01:06 +00:00
eafc6024cc
One of the best parts about concurrency in Rust is using `rayon` and how easy it makes parallelization of tasks, so it's the ideal example for parallel Rust on the web! Previously we've been unable to use `rayon` because there wasn't a way to customize how rayon threads themselves are spawned, but [that's now being developed for us][rayon]! This commit uses that PR to rewrite the `raytrace-parallel` example in this repository. While not a perfect idiomatic representation of using `rayon` I think this is far more idiomatic than the previous iteration of `raytrace-parallel`! I'm hoping that we can continue to iterate on this, but otherwise show it off as a good example of parallel Rust on the web. [rayon]: https://github.com/rayon-rs/rayon/pull/636
37 lines
952 B
JavaScript
37 lines
952 B
JavaScript
// synchronously, using the browser, import out shim JS scripts
|
|
importScripts('raytrace_parallel.js');
|
|
|
|
let booted = false;
|
|
let lastPtr = null;
|
|
|
|
// Wait for the main thread to send us the shared module/memory. Once we've got
|
|
// it, initialize it all with the `wasm_bindgen` global we imported via
|
|
// `importScripts`.
|
|
//
|
|
// After our first message all subsequent messages are an entry point to run,
|
|
// so we just do that.
|
|
self.onmessage = function(args) {
|
|
self.onmessage = event => run(event.data);
|
|
const [module, memory] = args.data;
|
|
wasm_bindgen(module, memory)
|
|
.then(() => {
|
|
booted = true;
|
|
if (lastPtr)
|
|
run(lastPtr);
|
|
})
|
|
.catch(e => setTimeout(() => { throw e; })); // propagate to main `onerror`
|
|
};
|
|
|
|
function run(ptr) {
|
|
if (!booted) {
|
|
lastPtr = ptr;
|
|
return;
|
|
}
|
|
lastPtr = null;
|
|
try {
|
|
wasm_bindgen.child_entry_point(ptr);
|
|
} catch (e) {
|
|
throw new Error(e.message + "\n\n" + e.stack);
|
|
}
|
|
}
|