stringer typewriter gets its export data from installed packages instead of source

[michaelsmanley]

Something I ran into today when generating code in a package whose exported declarations had changed between the version that was installed and the version that was being worked on.

golang/go#9702

Basically, if you read to the end, the tools authors expect people to use golang.org/x/tools/go/loader to get exported declarations from source.

The stringer tool itself has this same issue. It is a kind-of edge case, but for people using generators in actively-developed codebases, you can end up in a chicken-or-egg problem where you have to be able to install a package before you can run the generators on it.

[ibigpapa]

still an issue in go 1.8