You are right of course.
But given that `go list` is aware of other directives such as build
constraints I was wondering.
Anyways for go code generation, it would be very helpful to be able to have
a list of flies on which invoke go generate in the right order from `go
list`.
Giacomo
On
//go:generate is not limited to dependency on Go source files, so this
is not possible in the general case.
On Tue, 2020-11-10 at 01:05 -0800, gta wrote:
> Thanks for the reply,
> yes I know I can grep for those files, but I was hoping that go list
> could give me the files in the reverse
Thanks for the reply,
yes I know I can grep for those files, but I was hoping that *go list *could
give me the files in the reverse dependency order like *go list -deps*.
I was hoping to shave some time from our generation step.
I guess bash is my friend in this.
Giacomo
On Monday, 9
I know that you're asking about how to do this with the standard tools, but
you can do this with grep if you're on a platform that has the command
available:
grep --recursive --files-with-matches "//go:generate"
or, for short:
grep -rl "//go:generate"
This command will output a list of files
Hello,
is there a way to list all the files that have a `//go:generate` directive
with the standard tools?
I see that `go list` can show the ignored files so I am assuming it is
detecting `// +build ignore` directives, but I found nothing to lit the go
generate target files.
Thanks in
