Hands-On Dependency Injection in Go

What does this mean for Go?

In Chapter 1, Never Stop Aiming for Better, we mentioned the popular Go idiom coined by Jack Lindamood—accept interfaces, return structs. Combine this idea with the ISP and things start to take off. The resultant functions are very concise about their requirements and, at the same time, they are quite explicit regarding their outputs. In other languages, we might have to define the outputs in the form of an abstraction or create adapter classes to decouple our function from our users entirely. However, given Go's support for implicit interfaces, there is no need for this.

Implicit interfaces are a language feature whereby the implementor (that is, the struct) does not need to define the interfaces that it implements, ...