That would also be a weakness of most of the other proposals, including my own to add operators to interfaces. Contracts are more powerful, at the expense of extra complexity.
Andy > On Oct 18, 2018, at 10:34 AM, Ian Lance Taylor <i...@golang.org> wrote: > > On Wed, Oct 17, 2018 at 11:58 AM, Burak Serdar <bser...@ieee.org> wrote: >> >> Instead of specifying the minimal set of operations a type should >> satisfy, why not describe what the type should look like: >> >> func f(in like T) > > I don't see how this approach can handle multiple types that need to > work together in some known way, like the Graph/Node/Edge case in the > design draft. > > Ian > > -- > 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. -- 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.
