Re: [go-nuts] http.shutdownPollInterval documentation

:50:24 UTC, Ian Lance Taylor wrote: > > On Thu, Feb 22, 2018 at 1:50 PM, Sridhar <sridhar.ch...@gmail.com > > wrote: > > > > In https://golang.org/src/net/http/server.go the documentation for > > shutdownPollInterval (admittedly unexported) reads: > > >

[go-nuts] http.shutdownPollInterval documentation

In https://golang.org/src/net/http/server.go the documentation for shutdownPollInterval (admittedly unexported) reads: // Ideally we could find a solution that doesn't involve polling, // but which also doesn't have a high runtime cost (and doesn't // involve any contentious mutexes), but that

[go-nuts] [ANN] Stencil - Simple code templating for Go - a proposal and prototype

from Gonerics <https://github.com/bouk/gonerics>. The link above has more details and examples as well as some pros and cons of this approach. A prototype implementation can be found at https://github.com/sridharv/stencil. I'd love to hear your thoughts on this. Sridhar -- You re

Re: [go-nuts] Re: [ANN] lint - Run linters as part of go test

I've added support for gometalinter. Please take a look at the example in the godoc[1]. Thanks! Sridhar [1] https://godoc.org/github.com/surullabs/lint/gometalinter On Tuesday, November 15, 2016 at 10:41:40 AM UTC+1, sri...@laddoo.net wrote: > > Thanks for the feedback! > > Usin

Re: [go-nuts] Re: [ANN] lint - Run linters as part of go test

taticcheck >> >> import ( >> "testing" >> "github.com/surullabs/lint" >> ) >> >> >> func TestLint(t *testing.T) { >> if err := lint.Default.Check("./..."); err != nil { >> t.Fatal("lint failures: %v&

Re: [go-nuts] os.File re-definition

Ok I'll file an issue to start with. On Sunday, 4 September 2016 18:19:10 UTC+1, bradfitz wrote: > > Yeah, that'd be a fine cleanup. Want to send a change? > > I believe a similar cleanup happened to the net.Conn type a number of > releases ago. > > > > On Sat, Sep

[go-nuts] example in errors package documentation

The first example in the errors package documentation doesn't have anything to do with the errors package. How does one report this issue ? The golang/go issues has a Documentation label but that doesn't

[go-nuts] Same type different values

I need a little help understanding what's going on here: https://play.golang.org/p/8HydwIfgP3 The same type is being used to create 2 value pointers. Shouldn't the created pointers be equal ? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To