Egon Elbre

Sure, I can send them as Go CLs. And yeah, I have signed the CLA.

PS: I'll try to add *19 rule first, if I'm making it against Go, so one of the CL-s wouldn't be necessary -- i.e. https://github.com/golang/go/issues/67575

Unfortunately the general `* 19` optimization turned out to be more complicated. The performance varies based on the device and context. Anyways, submitted the CL-s with manual `*19` optimization https://go-review.googlesource.com/c/go/+/650277

You need to use the `shared` computation. From the root of your module, `goda graph "shared(./cmd/example:all, ./...)"`. * `./cmd/example:all` gets the set of all direct and indirect dependencies of the...

@nu11ptr I'm certainly open to adding a specific function or selector to do this behaviour. One of the problems with changing the default behaviour is that in principle it's a...

I added https://github.com/loov/goda/commit/6c77438ef3ab56d92ff6bcfc39460defba76f49f for the time being. The workspace information isn't readily available, so I'll wait until someone needs it. Hopefully this helps. Selecting from multiple modules is still a...

I completely understand the complexity sentiment. One of the problems is that the input for the program isn't a package per se, but a computation of what packages to include...

So, I have seen a few scenarios where you want to use `graph`: A. Small codebases, single package module, to visualize your dependencies to external packages. More for curiosity, rather...

After a few weeks I figured out a way that this would make sense... In other words introduce new behaviour when you don't have any arguments and automatically try to...

Unfortunately, I don't have merge rights. For some reason, I thought I had those permissions.