The static switch is a big problem. For any complex method you are going to completely duplicate all of the code. Not good.
Far better to map operators to interfaces then you only need a single method implementation. > On Sep 30, 2018, at 5:33 AM, Christian Surlykke <christ...@surlykke.dk> wrote: > > Hi > > I made a proposal for generics with constraints about ½ a year ago, which I > posted to the (very long) thread on issue 15292. I've now made a version 2, > in case anybody would like to read it. > > This version adapts to the generics syntax now proposed by the Go team and is > somewhat simpler than the previous version. > > br. Chr. > -- > 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.
