Code through go object files

[ha1dfo]

Hi folks,

We are trying to build bazel integration around golangci-lint.
Part of our current troulbes there: bazel builds go objects (ar packed binaries). These go object files seem to contain both the implementations and function fingeprints (much alike to .jar archives of .class compiled objects). It does it for both generated code and hand-written ones too.
However, when running golangci-lint against code that depends on anything like this, it's failing on unresolvable inputs.
I wonder, what's the recommendation: how would we parameterize golangci-lint to provide it with either the raw go object files or to the ar packaged one(s) -- so that it wouldn't need to have source code transitively to everything, but take the object file and assume it is correct?

[bombsimon]

Not an answer to your question, but wanted to start by mentioning that (better) Bazel support is discussed in #1473 as well. It seems like it also had some recent activity.