Feature Request: abortable about hash-wasm HOT 2 CLOSED

By default, WebAssembly is executed on the main thread. The only thing, which is parallelized, is the compilation of the binary: Chrome doesn't allow compiling larger binaries than 4kb in a sync manner. I also did some experiments running the hash calculation in Web Workers, but the communication latency is too high to be worth it. So the only reason, why hash-wasm is using promises, is because the restrictions imposed by the browser APIs.

Why would you need cancelation? In my point of view, the streaming input (createXYZ() functions) can be already used to hash large files in smaller blocks. You can stop anytime feeding update() with new chunks.

from hash-wasm.

You can stop anytime feeding update() with new chunks.

I guess I didn't think about that. I need to wrap these computations in asynchronous effects for another library, and as a part of the async effect spec, I need to be able to cancel. I will probably use the update then. I can't say I fully understand the performance characteristics of making new Wasm instance as noted in the README, but it does appear to be the way to run it in parallel.

It's good to know that the worker option wasn't valuable in many cases. Thanks.

from hash-wasm.