On Thu, 22 Sep 2022, at 11:27 PM, Rory Campbell-Lange wrote: I just wanted to respond to this part:
> I suppose my question is (and forgive me if this is a terrifically > naive), how can one negotiate the go landscape of commonly used modules > to re-utilise, where possible, a more commonly named interface > implementing "Speak()" or convertible to provide "Speak()"? > Generally, when writing Go, the consumer of the object defines the interface it requires. So rather than you looking for interfaces that might exist in the wild, it's better to focus on your application and its needs. If you have a component that uses the Speak method on objects then define that as an interface that your component can accept. Any other user of your component can see that interface is needed and provide a suitable object that implements it or create a shim to adapt one. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1fb8a3c4-b135-4ab1-b969-d6f4c239b7d9%40www.fastmail.com.
