Generics itself is a form of overloading, albeit in a very narrow sense. A generic function is in effect a set of functions (often infinite) where all the type parameters are replaced by those types which can conceivably satisfy any constraints placed upon them.
Anyway, assuming for the moment that I agreed with you that it was a bad thing for initialized types to have their own (non-generic) method set, the next question is how can you stop it? I suppose with solution #2 in my previous post, the compiler could 'look through' any type alias and disallow it when an attempt was made to declare a function with the type alias as receiver. You could still create a defined type rather than an alias: type FooInt Foo(int) but, presumably, there would be no problem in FooInt now having its own methods as they would be quite distinct from those of Foo(int). -- 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.
