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. On Wednesday, May 12, 2021 at 4:49:04 PM UTC+2 Bryan C. Mills wrote: > 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. > > On Wednesday, May 12, 2021 at 4:11:14 AM UTC-4 manlio....@gmail.com wrote: > >> 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` >> <http://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 >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/620f9cd1-4209-41c5-a3c3-a77c3854384dn%40googlegroups.com.
