[go-nuts] wasm, jsFunc, promises, blocking, sync vs async... quick question

Hello, Quick question. A JS function that calls into Go code via a Func wrapper (meaning it was defined in Go wasm code) is not allowed to block. Reason being that its execution blocks the event loop. Could that be relaxed so that we can cooperatively yield back to javascript? I am not sure it

[go-nuts] Re: wasm, jsFunc, promises, blocking, sync vs async... quick question

Ok seems to be related to that: Javascript Promise Integration On Saturday, July 12, 2025 at 5:26:55 PM UTC+2 atd...@gmail.com wrote: > Hello, > > Quick question. > A JS function that calls into Go code via a Func wrapper (meaning it was > defined in Go wasm code) is

[go-nuts] Enable importing vendor packages for bootstrap tools like cmd/compile, cmd/asm, ...

Currently, the bootstrap process of `./make.bash` generate a project in /pkg/bootstrap/src/bootstrap and then install bootstrap tools like compile, asm, link, etc. However, it does not support vendor package now, i.e. the go.mod in bootstrap project contains no vendor packages. It's just plain a

Re: [go-nuts] Enable importing vendor packages for bootstrap tools like cmd/compile, cmd/asm, ...

On Sat, Jul 12, 2025 at 6:55 PM Qingwei Li wrote: > > Currently, the bootstrap process of `./make.bash` generate a project in > /pkg/bootstrap/src/bootstrap and then install bootstrap tools like compile, > asm, link, etc. However, it does not support vendor package now, i.e. the > go.mod in boo