As per the spec <https://golang.org/ref/spec#Package_initialization>,
> A reference to a method m is a method value or method expression of the > form t.m, where the (static) type of t is not an interface type, and the > method m is in the method set of t. It is immaterial whether the resulting > function value t.m is invoked. In other words, the mere presence of an interface variable guarantees *no* dependency analysis? Here, I did a test <https://play.golang.org/p/8Fo4nUgGLBP>, but it indeed suffers the analysis. Any thoughts? -- 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/30500405-6f15-4f36-b49a-d082741ceb7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.