Re:Introduction to Go 1.1
by pcwalton on Tuesday March 26, 2013 @10:38AM
(#5443553)
Because if you had package A that defined type T, package B that defined method Foo on T and, separately, package C that defined method Foo on T, then B and C could not be linked together.
[ Parent
| on HN ]
I don't see why, personally, B defines Foo on T, so whenever B uses Foo, it should use B's Foo. C defines Foo on T, so whenever C uses Foo, it should use C's Foo. why is it ambiguous for the compiler which one to use?
If package D linked against B and C and called Foo(), which Foo() would it call?
Good question. If package B defined the function Bar(), and package C defined the function Bar(), then if package D linked to packages B and C, which function should it call when it asks for Bar()?
Naming collisions are a solved problem.
You don't have to import methods in Go; the compiler just finds them. They're in a per-type namespace and therefore would be vulnerable to collisions. Of course, they could change the language to allow/require you to import methods, but that would add some complexity.
On the other hand, you have to import functions, so your example isn't a problem.