I have read through most of the Go tour tutorial, but I'm still unclear on how Go's interface programming model compares with OOP?
Can someone explain how I can start 'thinking in Go'?
I'm confused how you can define an interface, and then create objects based on the interface?
Does Go implicitly create an concrete implementation for you during compile time?
分享 One of the problems OOP usually tries to solve is Polymorphism or the the ability for two different classes to have instances that behave the same. Usually in OOP this is accomplished by using inheritance. A Base class defines a minimal interface that other classes extend. All of the subclasses of Base class can be used as a Base class.
Go does the same thing not by inheritance but using interfaces. An interface is a "description" of behaviour. It is up to the individual Types in Go to satisfy this description by implementing each of the methods described in the interface. If a Type does implement all the methods described in the interface then it automatically satisfies the interface and can be cast to that interface automatically by the compiler.
分享
