Re: [go-nuts] when to use Sync pool

On Fri, Oct 6, 2017 at 1:23 PM, XXX ZZZ wrote: > > So we are making a platform where we have to use a TON of short lived > structs, in order to optimize this we intend to use sync pool, however on > our benchmark tests I have found that it only seems to improve

[go-nuts] when to use Sync pool

Hello, So we are making a platform where we have to use a TON of short lived structs, in order to optimize this we intend to use sync pool, however on our benchmark tests I have found that it only seems to improve performance when the struct is big enough, for smaller structs ie: (4-5 string

Re: [go-nuts] [security] Go 1.8.4 and Go 1.9.1 are released

On Fri, 06 Oct 2017 11:21:10 -0700 Rich wrote: Rich writes: > curl https://storage.googleapis.com/golang/go1.9.1.darwin-amd64.tar.gz | tar zxvf - > That will overwrite the existing /usr/local/go directory. To check: You are not alone in making this mistake. I made the *same*

Re: [go-nuts] [security] Go 1.8.4 and Go 1.9.1 are released

On linux / mac I just become root, cd to /usr/local then run this one liner: Mac: curl https://storage.googleapis.com/golang/go1.9.1.darwin-amd64.tar.gz | tar zxvf - Linux64: curl https://storage.googleapis.com/golang/go1.9.1.linux-amd64.tar.gz | tar zxvf - That will overwrite the

Re: [go-nuts] Hello, I have a question about the bottom of the goroutine

On Fri, Oct 6, 2017 at 9:22 AM, 王晚成 wrote: > hello ， > I have a question about the bottom of the goroutine. > What is the meaning of the mstartfn field inside the M structure > under runtime2.go? > Is this mstartfn the function that we write behind

[go-nuts] Hello, I have a question about the bottom of the goroutine

hello ， I have a question about the bottom of the goroutine. What is the meaning of the mstartfn field inside the M structure under runtime2.go? Is this mstartfn the function that we write behind the go statement? Or what other functions? Thanks very much!

[go-nuts] Re: [golang-dev] [security] Go 1.8.4 and Go 1.9.1 are released

Apologies, I missed that somehow. Thanks for the followup. Molly Crowther Cloud Foundry + Pivotal Security Team -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [go-nuts] Are all running goroutines killed when main ends?

This line of reasoning suggests an idea to me. Defer has the grammatical notion of "i want to do this later, but eventually, i don't want to forget to do it before i leave." Imagine the slightly stronger notion of a "will" as in a person's last will and testament. Actions in your will are steps

[go-nuts] Showing skipped tests in 'go test'

Dear gophers, I use feature detection and t.Skip for some of my tests, e.g. if !featureXPresent { t.Skip("feature X is not present" } which works well, but when running the tests I would like 'go test' to remind me that some tests were skipped. The only way I've found of listing the skipped

[go-nuts] Re: [golang-dev] [security] Go 1.8.4 and Go 1.9.1 are released

Just for the record, I have requested CVEs to be assigned to these issues yesterday. They got CVE-2017-15041 and CVE-2017-15042, respectively. It is already noted in the issues by rsc. JC - Original Message - > From: "Chris Broadfoot" > To: "golang-nuts"

Re: [go-nuts] Are all running goroutines killed when main ends?

I wrote a library to help with this https://github.com/ash2k/stager -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For

Re: [go-nuts] Are all running goroutines killed when main ends?

Thanks for clearing that up! On Thursday, October 5, 2017 at 9:52:30 PM UTC-7, Dave Cheney wrote: > > The only answer I have is to ask those goroutines to exit, the wait for > them to exit. Context is part of this, combined with a waitgroup to track > goroutines in flight. -- You received