On Tuesday, August 23, 2016 at 11:28:55 AM UTC+8, Jesse McNelis wrote: > > > Why a **T value can't call methods of *T and T if a *T value can call > methods of T? > > How many levels of auto dereferencing should there be? > Should *************T still have the same method set as *T? >
If a programmer will call it anyway, she/he doesn't care efficiency. What she/he cares is the convenience and cleanness. ppppppt.f() is surely cleaner than (*****ppppppt).f(), right? > It's reasonable to set a sensible limit because pointer chasing is an > expensive operation. > So for anything more indirect than *T you need to explicitly show the > dereferencing. > -- 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.
