Hello,
Is there any programmatic way of disabling cgo runtime checks?
The documentation says to set environment variable "GODEBUG=cgocheck=0".
However, this does not work for me as I do not control the environment.
Hoping there is a programmatic way for disabling the runtime checks?
Regards,
Sr
gt; Sleeping in time.Sleep does not count as running.
>
> If you mean something else, can you be more specific? My apologies if
> I'm missing something.
>
> Ian
>
> > On Monday, October 3, 2016 at 12:04:39 PM UTC-7, Ian Lance Taylor wrote:
> >>
> >
calls can result in other goroutines being used? Would a
network call waiting for IO result in a goroutine context switch?
Thanks in advance.
On Monday, October 3, 2016 at 12:15:18 PM UTC-7, Ian Lance Taylor wrote:
>
> On Mon, Oct 3, 2016 at 12:10 PM, 'SrimanthG' via golang
If you run the code snippet I pasted in
https://play.golang.org/p/4R-WlCiKNT you will see that it runs both in
parallel - hence my confusion
On Monday, October 3, 2016 at 12:04:39 PM UTC-7, Ian Lance Taylor wrote:
>
> On Mon, Oct 3, 2016 at 11:31 AM, 'SrimanthG' via golang
Hello,
I ran a Go program with GOMAXPROCS=1 and two goroutines which both did
"runtime.LockOSThread()" and slept 10 seconds before exiting.
Code: https://play.golang.org/p/4R-WlCiKNT
Since I had 1 OS thread and 2 goroutines trying to lock an OS thread, I was
expecting only one of them to comple