/explore
|
You are here 
|
jordanorelli.com | ||
| | | | |
www.integralist.co.uk
|
|
| | | | | Interfaces in Go Name Your Interface Arguments Keep Interfaces Small Accept Interfaces, Return Concrete Types Don't Return Concrete Types Use existing interfaces Don't Force Interfaces Embedding Interfaces Upgrading Interfaces Standard Library Interfaces Tight Coupling Dependency Injection Refactoring Considerations Testing More flexible solutions? Conclusion This post is going to explain the importance of interfaces, and the concept of programming to abstractions (using the Go programming language), by ... | |
| | | | |
masnun.com
|
|
| | | | | In Go or Golang, declaring an interface is pretty simple and easy. type Printer interface { Print(string) } We just defined an interface named Printerthat required an implementer to have a method named Printwhich takes a stringparameter and returns nothing. Interfaces are implemented implicitly in Go. Any type that has the Print(string)method implements the interface. [...] | |
| | | | |
www.alexedwards.net
|
|
| | | | | ||
| | | | |
www.chriswarbo.net
|
|
| | | [AI summary] A discussion thread clarifying misconceptions about state, the IO monad, and functional purity in Haskell by explaining how the language represents imperative programs as pure data structures. | ||
