Sam Clegg

Ah yes, `nextWorkerID` is debug-only feature.

I would rather you use the existing nextWorkerID, but only add the `-N` suffix when `ASSERTIONS` are enabled.

> I'd prefer to always have worker thread IDs. Without IDs debugging is just pure pain. > > But I've just pushed a commit which puts `#if ASSERTIONS` around it....

If you have a proposed fix then that would be most welcome. However, I don't know of anyone who works on wabt who has time to devote to fixing this...

We do a lot of building with of all our library with a lot of parallelism, but I don't think i've run into this issue locally or in our CI....

I wrote a test to try an repro this but so far its not reproducing: #25772

As with any callback-based API you just need to yield to the event loop while you wait for the results. There are several ways to do that. See https://emscripten.org/docs/porting/emscripten-runtime-environment.html#browser-main-loop. The...

`ASYNCIFY` is really just last resort for folks that cannot easily break up their main loop

Can you explain, perhaps with an example? I'm pretty sure WebGPU does not depend on use of ASYNCIFY. I imagine when you use an asynchronous operator to create your shader...

Without ASYNCIFY (or JSPI) you would need to rewrite your `BufferWebGPUImpl::Map` function to itself be async (i.e. either take callback functions or return some kind of future/promise object).