proposal: ignore stale information in go list -find -json

[Manlio Perillo]

The go list `-find` flag was introduced to skip resolving imports.

However, is it really necessary to include stale information in this case?

Does `golang.org/x/tools/go/package` need it?

Getting stale information is not a trivial work, AFAIK.

Is it ok to change the meaning of an existing flag?

Thanks

Manlio

[Bryan C. Mills]

https://golang.org/issue/29666 (still open) is the general issue for avoiding unnecessary work in 'go list'.

It isn't obvious to me which kind of stale information we can omit for 'go list -find' in particular.

[Manlio Perillo]

I was suggesting to not use work.Builder in the go list command, even in case the -json flag is specified or the -f flag contains the ".Stale" string.

I'm not sure about the -f flag, however, since it is an explicit request from the user.  On the other hand, if the user specified the -find flag, probably don't really want expensive data.

As for the -json flag, it may be considered a change to the public API, but I'm not sure.

Thanks.