On Tue, 30 Jul 2019 at 14:58, <alan.f...@gmail.com> wrote: > One way of avoiding this muddle between pointer and value methods would be > to require that any type parameter (T say) which is subject to a contract > cannot be replaced by a pointer type. >
What do you mean by this? Do you mean you can't use a pointer type as a type parameter? That would seem rather restrictive to me. For example, AFAICS it would mean you couldn't have a single function that is able to call a String method on both `*big.Int` and `reflect.Type`. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAJhgachqD_dG1QWG9CG3zudzCCuJ_ctKK2MWMdQbk8Kp1aW0Gw%40mail.gmail.com.
