Re: [go-nuts] syscall/js: strange deadlock caused by wasm event handling callback (runtime bug?)

2022-08-06 Thread at diar
Doesn't seem that this is a known issue. I will try and write a short reproducer and file an issue. On Fri, Aug 5, 2022, 11:18 PM atd...@gmail.com wrote: > Hi, > > I have a little concurrency problem. Seems that my Go-wasm-defined event > handlers run concurrently instead of synchronously. > > B

Re: [go-nuts] Type parameters syntax... Can it be improved?

2021-03-25 Thread at diar
Yes that too. To differentiate between MinFloat and MinInt for instance. :) On Thu, Mar 25, 2021, 8:18 AM Martin Leiser wrote: > > > Ian Lance Taylor schrieb am Dienstag, 23. März 2021 um 23:22:51 UTC+1: > >> On Tue, Mar 23, 2021 at 3:19 PM atd...@gmail.com >> wrote: >> > >> > Since, we also

Re: [go-nuts] Re: Type parameters syntax... Can it be improved?

2021-03-24 Thread at diar
Yes, and... (just in case someone else comes across this thread wondering in the distant future) , func(v T) T is not too big a problem but func(v T) R If the function body has cases, i.e. flow sensitive, that's where the brackets are mandatory to make the inference more straightforwardly decidab

Re: [go-nuts] sycall/js : does it require build tags? if so whihc ones?

2021-01-31 Thread at diar
Thanks. I think I figured it out. Apart from the build tags that you have mentioned, depending on the code editor, the build tool need to be specified GOOS and GOARCH too. And some of the old code completion tools do not support the new syscall/js package. In my case, using atom.io, I had to laun