<p>(Compared to a pointer receiver)
As quoted "A value receiver can reduce the amount of garbage that can be generated; if a value is passed to a value method, an on-stack copy can be used instead of allocating on the heap." in <a href="https://github.com/golang/go/wiki/CodeReviewComments">https://github.com/golang/go/wiki/CodeReviewComments</a></p>
<p>From what I imagine a pointer receiver will be treated just like a value receiver whose value is a pointer. And that pointer value is stored in stack rather than generated on heap. Am I missing something?</p>
<hr/>**评论：**<br/><br/>dbud: <pre><p>This is more of an escape analysis issue. If the compiler can't tell if the thing you are calling stores the pointer, it has to put your object on the heap so the pointer can live past that single function invocation.</p>
<p>Not sure what all the analyzer can determine, so that may be an older issue. I believe the compiler has flags to report escape analysis issues, not sure.</p></pre>ctcherry: <pre><p><code>-gcflags -m</code></p></pre>
