<p>I'm sure there's gotta be some golang spec or design explanation somewhere, but it seems as if it doesn't matter if I call a method with the data struct directly or if it's a pointer... I know that if I modify things, it needs to be the pointer if I want to change the original object, but that's not the question here. I understand that part just fine. I've explained this badly, so here is an example:</p>
<p><a href="https://play.golang.org/p/crgezmdAXY">https://play.golang.org/p/crgezmdAXY</a></p>
<p>Why does this work? Why <em>should</em> it work? I guess I'm the first golang user who is unhappy when something works. Actually, I'm not unhappy, but I would like to understand the why.</p>
<p>Thanks!</p>
<hr/>**评论：**<br/><br/>ctcherry: <pre><p><a href="https://golang.org/ref/spec#Calls">https://golang.org/ref/spec#Calls</a></p>
<p>A method call x.m() is 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 &x's method set contains m, x.m() is shorthand for(&x).m()</p></pre>singron: <pre><p>See <a href="https://golang.org/doc/effective_go.html#pointers_vs_values">https://golang.org/doc/effective_go.html#pointers_vs_values</a></p>
<p>The gist is that Go will convert from a pointer to a value to call a method with a value receiver. It will also covert the other way if the value is addressable.</p></pre>sandokan1572: <pre><p>It will make a difference once you start changing the receiver. It also makes a difference when considering whether given type implements an interface.</p></pre>
