[go-nuts] Re: It was removed some packages from go.googlesource.com

2018-04-24 Thread theckman via golang-nuts
This should now be fixed. Here's the RCA: - https://github.com/golang/lint/issues/397#issuecomment-383994496 Cheers! -Tim On Monday, April 23, 2018 at 6:58:55 AM UTC-7, takanao ENDOH wrote: > > Hi, guys. > > Could not `go get golang.org/x/lint/golint` > . > Is

[go-nuts] Re: It was removed some packages from go.googlesource.com

2018-04-24 Thread theckman via golang-nuts
Hey Gary, This isn't a leftpad moment. Your code can still be compiled, and there's a not too invasive workaround: - https://github.com/golang/lint/issues/397#issuecomment-383752949 Our leftpad moment was a few months ago when this repo disappeared: - https://github.com/jteeuwen/go-bindata -

Re: [go-nuts] Question about the spec: Method Sets and Pointer Receivers

2018-02-06 Thread theckman via golang-nuts
Hey Gregg I think that would make it more clear and looks great. I wouldn't want to take credit for your copy, but I'd be happy to open an issue / PR with this change. I'm not sure how to best attribute it to you. Cheers! -Tim On Monday, February 5, 2018 at 2:35:47 PM UTC-8, Gregg Townsend

Re: [go-nuts] Question about the spec: Method Sets and Pointer Receivers

2018-02-05 Thread theckman via golang-nuts
valid if the method set of (the type of) x > contains m and the argument list can be assigned to the parameter list of > m. If x is addressable and 's method set contains m, x.m() is shorthand > for ().m()" > > > Paul > > On 5 February 2018 at 17:42, theckman via golang-

[go-nuts] Question about the spec: Method Sets and Pointer Receivers

2018-02-05 Thread theckman via golang-nuts
Hey Gophers, I've run in to an interesting case regarding Method Sets that makes me wonder whether it should be disallowed by the spec[1]. Before opening an issue on GitHub I thought I'd reach out here to get some clarifications as I may be misreading the spec. Based on my understanding of