It is rather the point of interfaces that there IS no fixed definition of an instance of an Interface call. The definition could be that of ANY struct that matches that interface, depending on what is passed.
So yes, you have to find AN instance of a call to the function that accepts an interface, to find out what it is calling. Because if you call it with a different struct, it calls that struct's implementation. Kind of the point. And finding that implementation for that call does not guarantee that the next call may not be calling a different implementation, because it is being passed a different struct. Your steps after 5 seemed a bit unnecessary - just go to the definition of xooConn, your step 5, and search for Close. While it is possible to implement a function on a struct elsewhere, the likelihood is pretty low, and if you don't find it, then you can go on to your other steps. -- 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. For more options, visit https://groups.google.com/d/optout.
