On Thursday, 11 May 2017 12:39:18 UTC+2, mhh...@gmail.com wrote: > > > I d only remark about this, > > so there are actually just two cases: Method is on pointer receiver or > not. > > From the declarer side, > there is indeed only 2 cases, > which accounts for 50% of the whole, > declaration + consumption, > the consumer is still accountable for the remaining > 50% of the instance consumption and usage. > > I do not agree. Your "other 50%" are indistinguishable, they have no observable difference. Most people do not think if 1+1+1, 1+2, 2+1 and 3 as four *different* things, for basically all natural usage these four things are just one, the number 3. It is the same here:
var p *T p.M(), (*p).T, (&(*p)).T and so forth might be formally different but they are not. There a two things. Methods on pointer receivers and method on values and it does not matter in reasoning about the behaviour of the code on how the method is invoked. V. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
