3 ms·
I believe it's basically just bundling the runtime, so yes, it's concurrent, however WASM doesn't provide threads I believe so it's still effectively running si
by ecnahc515 8y ago
I believe it's basically just bundling the runtime, so yes, it's concurrent, however WASM doesn't provide threads I believe so it's still effectively running single threaded (ie: same as GOMAXPROC=1).
- 4ad 8y agoNo, GOMAXPROC=1 is not single threaded. GOMAXPROCS=1 uses one kernel thread for running user Go code, but it uses other kernel threads for running system (runtime) Go code, or for executing system calls. More details: https://news.ycombinator.com/item?id=12460807 https://news.ycombinator.com/item?id=12460807
- amelius 8y agoYes, but if WASM is single-threaded, then how can the GC run in a different thread?
- 4ad 8y agoI don't have a deep understanding on how the WASM Go port works, sorry. I was simply responding to the parent comment about GOMAXPROCS=1. I suspect the WASM port is single threaded and blocks in the GC, but I am not an expert on this.