Re: [go-nuts] Alternative way of setting cgocheck=0

2017-11-16 Thread 'Srimanth Gunturi' via golang-nuts
My environment is unable to accept this format due to the double '=' in the same key/value. Is there an alternate way of expressing the same environment variable - like 'GODEBUG=cgocheck:0' or something like that? On Wed, Nov 15, 2017 at 9:05 PM, Ian Lance Taylor wrote: > On Wed, Nov 15, 2017

Re: [go-nuts] runtime.LockOSThread() question

2016-10-03 Thread 'Srimanth Gunturi' via golang-nuts
Now it is making more sense. So GOMAXPROCS has no connection with the actual number of OS threads created to run goroutines. But it does determine how many of them are active at any given time. Also, a single OS thread can multiplex multiple goroutines, unless #LockOSThread() is invoked in which ca