[go-nuts] Go coaching in palo alto, mountain view

I’m looking for an experienced go developer that I can rent for an hour a week to answer questions, explain thing about the go toolchain, libraries and runtime. Thanks, Joe -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from t

[go-nuts] Re: running godoc in a dir outside gopath

Currently, godoc will only show documentation for GOPATH and GOROOT. Work is being done to make godoc work with modules. Feel free to subscribe to https://github.com/golang/go/issues/26827. On Monday, 29 July 2019 04:46:48 UTC+5:30, DrGo wrote: > > Hello, > > Wondering what I am doing wrong. >

[go-nuts] Re: Quick question about the new Contracts Draft Proposal

https://go.googlesource.com/proposal/+/master/design/go2draft-contracts.md (Updated on 7/25/2019) GopherCon 2019 Talk summary: https://about.sourcegraph.com/go/gophercon-2019-generics-in-go Jon On Sunday, July 28, 2019 at 7:55:50 PM UTC-4, Mandolyte wrote: > > I missed this. Do you have a link

[go-nuts] Quick question about the new Contracts Draft Proposal

I missed this. Do you have a link to the proposal? -- 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. To view this discussi

[go-nuts] Re: P-local/M-local storage for goroutines?

For reads, 1. Use lock-free ring buffers to record the read events, don't update the eviction policy. 2. Have an array of buffers and use the key's hash to select one 3. Drop the read event if contention or the buffer is full 4. When full, use a try-lock to replay the events against the eviction

[go-nuts] running godoc in a dir outside gopath

Hello, Wondering what I am doing wrong. Using go13.beta1 (Darwin), I am running a freshly downloaded godoc in a dir that includes several of my own packages like this godoc -http=localhost:6060 -goroot ~/local/git/ But on the browser, godoc is simply serving a list of all files in the dir (no

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,

[go-nuts] Quick question about the new Contracts Draft Proposal

Hello, I did a first read through the proposal and it looks very good. I had one question: when giving the example of how to implement Sorting using orderedSlice, the type parameter is declared to be comparable. Should that be contracts.Ordered? Thanks, Jon -- You received this message be

[go-nuts] Re: go 1.13 changes

rob solomon, Go 1.13 Release Notes: https://tip.golang.org/doc/go1.13 peter On Sunday, July 28, 2019 at 12:02:14 PM UTC-4, rob wrote: > > I recently saw a description including rationale and historical > references regarding the new features being added to version 1.13. > > Now I cannot find

[go-nuts] go 1.13 changes

I recently saw a description including rationale and historical references regarding the new features being added to version 1.13. Now I cannot find that description on the site. Where is it?  What's the url? --rob solomon -- You received this message because you are subscribed to the Google