Hallöchen! Jan Mercl writes:
> On Sat, Jul 16, 2016 at 10:39 AM T L <tapir....@gmail.com> wrote: > >> I know this result, but I just need the reason, not the result. > > The method set distinction of T vs *T allows to forbid calling > methods intended to mutate the receiver (ie. receiver is *T) on > the wrong receiver type (T). There still is a subtle asymmetry: a.b() is implicitly converted to (&a).b() if necessary. Why isn't f(v) implicitly converted to f(&v) if necessary? Tschö, Torsten. -- Torsten Bronger Jabber ID: torsten.bron...@jabber.rwth-aachen.de -- 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.
