Re: [go-nuts] Making a copy of a pointer receiver

Yes.
Incorrect. http://play.golang.org/p/jG9vEOvxUs

Of course, the value type does not implement the interface, but that's
to be expected.



Thinking on when I use value methods, I think it's just for clarity;
mixing value recievers and pointer recievers creates a bit of confusion
when most methods mutate the value. The * in the declaration is really
easy to miss; it's clearer if everything is the same.

This is valid: http://play.golang.org/p/zDt6LxHDlT
This is valid: http://play.golang.org/p/weuozddq3r
This is valid: http://play.golang.org/p/282YC5RXxw
This is not valid: http://play.golang.org/p/GM7E24w4nL
This is not valid: http://play.golang.org/p/aPHACbAisZ

The rule about pointers vs. values for receivers is that value methods can
be invoked on pointers and values, but pointer methods can only be invoked
on pointers
I don't think you absorbed the full context of the quoted text. You kind of
just read that last line.

Can't mix receiver types with values and pointers and expect it to
implement an interface, all methods satisfying an interface must implement
the same method set including the same receiver. And in the case of your
example, it is just one of those quirky exceptions and compiler magic saves
the day.

http://golang.org/doc/effective_go.html#pointers_vs_values

thank you both.

this is a bit embarrassing. i read the spec often enough but somehow did
not connect the Method Sets with the Interface types section.

and sorry chris for not checking the spec before sending out the mail.
but in my defense it was from my phone.