Kamil Kisiel

I'm not sure that would work. errcheck relies on `go/types` and `go/build` to analyze the code and generally that requires the entire entire package.

Ah ok, that seems reasonable. I don't think it would be too hard to add. Do you know how to find a package given a filename?

Great, thanks. I figured this was something someone would have solved already :) I'll try to whip up a patch some time soon On Sat, Aug 13, 2016 at 12:39...

yeah I think it makes sense to resolve everything to absolute package paths

Actually I think #40 addresses that, sorry it's been a while since I looked. Do you mind giving that PR a try, and if it works for you, I can...

Can you give some more details on what your problem with the -p flag is?

Do you mean -o? -p is for filtering out prefixes. (alias for -ignoreprefixes)

yes, this package was written quite a long time ago and uses much more primitive methods of traversing the dependency graph than are now available in Go.

You could always just use a copy of the code of `go list` and bypass the exec and json steps. It should be much faster that way.

A similar request exists for kisielk/errcheck#75 One problem is there's no API available for loading vendored packages at the moment, it seems the only support is directly in cmd/go so...