Re: [go-nuts] LockOSThread, switching (Linux kernel) namespaces: what happens to the main thread...?

On Wed, Jun 1, 2022 at 10:45 AM TheDiveO wrote: > > While exploring more of the proc.go code I noticed that my original question > somehow didn't fully reflect what I'm wondering about: what happens in the > following situation...? Are all tasks/threads really equal? > > a non-main G42

Re: [go-nuts] [ANN] Event Horizon - first realease of CQRS/ES library

Hi Max I am trying to learn to implement eventhorizen is there possibility to give me little example of implementation. existing sample bit complected for as i am still learning this ddd concept. thanks so much cheers Bimal On Sunday, 23 November 2014 at 01:27:48 UTC+11 Max Ekman wrote: >

Re: [go-nuts] [security] Go 1.18.3 and Go 1.17.11 are released

Hi Jakob, The go-gettable golang.org/dl/go1.18.3 command is published and might take a moment to propagate. You can either try again in a short while, or do something like 'go install golang.org/dl/go1.18.3@HEAD'. (The '@HEAD' suffix is one of the ways to explicitly request that particular git

Re: [go-nuts] [security] Go 1.18.3 and Go 1.17.11 are released

On 1 Jun 2022, at 22:58, Dmitri Shuralyov mailto:dmits...@golang.org>> wrote: Hello gophers, We have just released Go versions 1.18.3 and 1.17.11, minor point releases. These minor releases include 4 security fixes following the security policy: Hi Dmitry, Thanks

[go-nuts] [security] Go 1.18.3 and Go 1.17.11 are released

Hello gophers, We have just released Go versions 1.18.3 and 1.17.11, minor point releases. These minor releases include 4 security fixes following the security policy : - crypto/rand: rand.Read hangs with extremely large buffers On Windows, rand.Read will hang

[go-nuts] Re: syscall/js: wasm perf question

Seems like it might be a slow handling of wasm in Chrome. Firefox is almost twice as fast. There seems to be almost no overhead. On Tuesday, May 31, 2022 at 3:19:24 PM UTC+2 atd...@gmail.com wrote: > Hi, > > I am trying to optimize some wasm code that runs into the browser. > So far, the

Re: [go-nuts] LockOSThread, switching (Linux kernel) namespaces: what happens to the main thread...?

While exploring more of the proc.go code I noticed that my original question somehow didn't fully reflect what I'm wondering about: what happens in the following situation...? Are all tasks/threads really equal? - a non-main G42 goroutine gets scheduled onto the main thread/leader task,

[go-nuts] When compiling into an iOS header file, expect to return **Nullable** String

If I have the following golang code ``` package sdk type Person struct { } func (p *Person) GetName() (string, error) { return "", errors.New("...") } ``` When I package it as xcframwork, its header file will probably look like this ``` *@interface* SdkPerson : NSObject {} // ... -

Re: [go-nuts] Nil could be the zero value for type variables

On Wed, Jun 1, 2022 at 9:05 AM Brian Candler wrote: > On Wednesday, 1 June 2022 at 02:19:43 UTC+1 Ian Lance Taylor wrote: > >> We could do that. The main concern is that "nil" is already >> overloaded, and people new to Go are frequently confused by it. See >> the FAQ entry

Re: [go-nuts] Nil could be the zero value for type variables

On Wednesday, 1 June 2022 at 02:19:43 UTC+1 Ian Lance Taylor wrote: > We could do that. The main concern is that "nil" is already > overloaded, and people new to Go are frequently confused by it. See > the FAQ entry https://go.dev/doc/faq#nil_error . Adding more uses of > nil will increase the