Re:Interfaces in Go make it hard to navigate code
by jitl on Monday May 27, 2013 @04:42AM
(#5773925)
There can definitely be a problem here if you've built very complex interfaces - but that isn't the "Go Way." The documentation suggests make one- or two- method interfaces, with interface names that suggest the methods you must implement. The interface name is the required function + "er". Hence if you have an interface "Peeker" you can expect that the method types must implement is "Peek".
[ Parent
| on HN ]
There are no comments on this comment yet.