On Fri, Sep 14, 2018 at 10:47 AM, <alan.f...@gmail.com> wrote: > > The problem is that many people think the current draft design is too > complex and I haven't seen a plausible suggestion from anyone (myself > included) which would be appreciably simpler but as comprehensive, or nearly > so. > > This is why I'd concluded that, if a system could be devised which was > simple but nonetheless addressed 90% of the use cases for generics, it might > be good enough.
We've been working on this for years. It's far too soon to give up on a reasonably complete solution. And, as I tried to say earlier, a 90% solution has its own complexities. If the only reason to reject the design draft is complexity, then it's not obvious that a 90% solution is really simpler. And, of course, we're only really going to understand the complexity of the design draft when we can try writing real code that uses it. 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.
