[go-nuts] Why will it deadlock if a goroutine acquire a mutex while pinned to its P?

I'm reading this commit https://github.com/golang/go/commit/d5fd2dd6a17a816b7dfd99d4df70a85f1bf0de31 . Inside runtime_procPin we only increases the m.lock count, why will it cause deadlock when acquiring a mutex after pin? -- You received this message because you are subscribed to the Google

Re: [go-nuts] Confusion regarding templates and iterating over map

On Mon, Apr 8, 2019 at 2:41 PM Ian Lance Taylor wrote: > On Sun, Apr 7, 2019 at 6:19 PM Amit Saha wrote: > > > > I am seeing (what I think) a somewhat confusing behavior which I am not > sure I understand. The working code example is at > https://play.golang.org/p/GEqT4MiZQnq > > > > > > Basical

Re: [go-nuts] Confusion regarding templates and iterating over map

On Sun, Apr 7, 2019 at 6:19 PM Amit Saha wrote: > > I am seeing (what I think) a somewhat confusing behavior which I am not sure > I understand. The working code example is at > https://play.golang.org/p/GEqT4MiZQnq > > > Basically, I have a map which I am iterating over in a template: > > > m :

[go-nuts] Confusion regarding templates and iterating over map

Hi all, I am seeing (what I think) a somewhat confusing behavior which I am not sure I understand. The working code example is at https://play.golang.org/p/GEqT4MiZQnq Basically, I have a map which I am iterating over in a template: m := map[int]string{ 1: "\"Hello\"\n", 2: "\"World\"\n",

Re: [go-nuts] Re: [ANN] Gomail v2: sending emails faster

If those black boxes represent Go language code, please share it here by pasting it into the Go Language Playground and then sharing a link in email here. It is impossible to understand these rectangles on my phone. On Sat, Apr 6, 2019 at 11:10 PM wrote: > hi, i use this code, I can't make it w

Re: [go-nuts] Modifying the Runtime Scheduler

Should be public now, thanks for bringing that to my attention. On Sunday, 7 April 2019 20:41:41 UTC+2, robert engels wrote: > > The link to the repo does not allow not credentialed access... > > On Apr 7, 2019, at 5:58 AM, Tharen Abela > > wrote: > > I'll preface this by saying this is for acade

Re: [go-nuts] Modifying the Runtime Scheduler

The gist of the problem is that I am allocating an object in the runtime, (which I refer to as the batch struct), and the GC is deallocating the object, even though a reference is being kept in a slice (similar to *allp* and *allm*). While allocating, I call *acquirem* to prevent the GC being tr

Re: [go-nuts] Modifying the Runtime Scheduler

I think it would be helpful to if you providee a summary of the issue/idea before the detailed information - it makes it nearly impossible to understand - at least for me. > On Apr 7, 2019, at 1:41 PM, robert engels wrote: > > The link to the repo does not allow not credentialed access... > >

Re: [go-nuts] Modifying the Runtime Scheduler

The link to the repo does not allow not credentialed access... > On Apr 7, 2019, at 5:58 AM, Tharen Abela wrote: > > I'll preface this by saying this is for academic purposes. > > I am working in the following repository > , but the following files are the

Re: [go-nuts] Re: Some issues with UDP and Go

I am not sure that is the case. It is “known” that UDP doesn’t support OOB, mainly since it is not a stream - it is packet oriented, but also because it is not part of the specification - it would have to be an application level transport that adds that as far I understand. That being said, I a

[go-nuts] Re: Some issues with UDP and Go

Thanks, that makes sense. So the documentation here needs some work since that is not at all clear. On Sunday, April 7, 2019 at 11:42:52 AM UTC-4, Pelle Johansson wrote: > > Hi John, > > The oob data used in these system calls are not for communicating with the > peer. UDP doesn't support OOB d

[go-nuts] Re: Some issues with UDP and Go

Hi John, The oob data used in these system calls are not for communicating with the peer. UDP doesn't support OOB data on the wire, I think the name here is a bit unfortunate, it should rather be called "control" or somesuch. This data is processed/created locally by the kernel and its structur

[go-nuts] Re: CompileError: AsyncCompile: Wasm decoding failed

Well I solved this one, and here was the solution for me for any that it might help. When I wrote my initial test.go program (Hello world) it was in the same path as my main.go and both were using the function 'main'. Well, I renamed the function in the test.go simply to 'test' and compiled t