Ingvar Stepanyan
Ingvar Stepanyan
FWIW (for others coming across this issue) these days I use Godbolt instead - it can show Wasm too (albeit in custom text format used by LLVM instead of standard...
> Hm, but that doesn't show the function signature, and seeing how the function arguments get compiled to wasm was the entire reason why I wanted to look at the...
Hm so looking at those "another process has device opened for exclusive access", does that mean that on macOS it's not possible to libusb_open same device multiple times? Is this...
If it's the latter, one thing that could be done is to use reference counting in the backend's device wrapper. But first would be good to understand where this limitation...
I'll probably leave further investigation to macOS backend maintainers. But this looks like exactly the kind of issues with concurrent transfers I was hoping the updated test would help reveal,...
Hm, I just tried again and can't reproduce this anymore. Given that the pinned Rust version hasn't changed, I suspect it must've been either a bug in wasm-bindgen or in...
Linked issue was resolved, so this should work nowadays. If not, please open an issue on the new repo (https://github.com/RReverser/wasm-bindgen-rayon).
Latest version of wasm-bindgen-rayon allows to use Rayon directly from the main thread, without extra Worker and Comlink.
I guess I'll close this since resolver=2 has been the default for some time now and, in my understanding, avoids the related issue.
@vdjeric Probably would be worth to archive the repo (for whoever has the rights to do so) to avoid confusion.