> in Java, I frequently ask my tools, "Give me a list of
> classes that implement this interface,"
You don't generally ask this question when working in Go, because you don't really construct your "type" system in these terms. > in Java, I frequently ask my tools, "Give me a list of
> classes that implement this interface,"
You don't generally ask this question when working in Go, because you don't really construct your "type" system in these terms.
How well does that work with tooling? For example, in Java, I frequently ask my tools, "Give me a list of classes that implement this interface," and I expect a fast and -- most important -- 100% accurate answer.
My instinct is that Go's approach makes it tooling-unfriendly (a good chance of false positives, especially in large systems), but perhaps I'm missing something.