Re:Things about programming I learned with Go
by literallycancer on Tuesday August 22, 2017 @08:56AM
(#15071870)
What's the issue with composing a new type that has otherPackage.Receiver in it, and defining the new method on the new type?
[ Parent
| on HN ]
Re:Things about programming I learned with Go
by leaveyou on Tuesday August 22, 2017 @09:08AM
(#15071963)
For me there is no issue.
Re:Things about programming I learned with Go
by ptman on Wednesday August 23, 2017 @08:15AM
(#15080815)
I'm guessing: you still can't access unexported members (private vs Public).
Re:Things about programming I learned with Go
by junke on Tuesday August 22, 2017 @03:28PM
(#15075611)
The question could be asked the opposite: why is the new type necessary?
Re:Things about programming I learned with Go
by majewsky on Tuesday August 22, 2017 @05:21PM
(#15076506)
Because if you allow non-local method declarations, you have a ton of stuff to think about:
- Are these methods exported?
- If yes, how do you import them? Explicitly or implicitly?
- Given a method call, how can the developer tell where it was defined? How can she know if the same method call is available when using the same library in some other project? Remember that not everyone uses IDEs.
- etc.
I can see why the Go designers decided that it's just not worth it. I've seen how you turn a language into a mess with non-local method declarations (cough Ruby cough).