[go-nuts] A question about go bug template

In the go bug template, go version is printed twice, the first time in the "go version" section and the second time in the "details" section as GOROOT/bin/go version. After https://golang.org/cl/288693 , these two entries should show the same version. In order for them to differ, one should do

Re: [go-nuts] A question about go tool trace scheduler time

Also, based on the number of Go routine 4k, and the Go routine ID - you may be cycling through threads really rapidly, if the Go routines are using blocking calls that are spawning new threads - as these spin up you will increase the scheduler wait time. > On Jul 28, 2019, at 4:42 PM, robert en

Re: [go-nuts] A question about go tool trace scheduler time

goanalyzer might help you understand what is happening better. The schedule wait time looks high, but this time is dependent on the number of active (usually CPU bound) Go routines vs. GOMAXPROCS (which is usually limited by number of CPUs). > On Jul 27,

Re: [go-nuts] a question about go

Because 3.0 == 3 and the documentation for the fmt package says the default verb (%v) for floats prints only so much digits as needed, which also implies training zeros will be dropped until explicitly asked for by a different formatting verb, like %f3.1, for example. On Thu, Dec 20, 2018, 18:29 J

[go-nuts] a question about go

This is the code I find when I read the a book about Golang. I have a question why the result is 1,2,3,4 instead of 1, 2, 3.0 and 4.0 when bx and by are float. Could anyone help me? Thanks a lot! [image: Screen Shot 2018-12-20 at 11.59.07 PM.png] -- You received this message because you are