Jay Conrod

@excavador We're still developing a more complete solution to this (the workspace abstraction I mentioned above). Ideally, tools won't need to be aware of the project layout in use. I...

The workspace abstraction mentioned above is being actively worked on. We've gone through a lot of internal prototypes, and we're in the process of reviewing, testing, and merging one that...

Not yet, but soon. We're still working on simplifying and narrowing the interface.

The first public piece of this is [`golang.org/x/tools/go/packages`](https://godoc.org/golang.org/x/tools/go/packages). At the moment, that is based on `go list` and is intended to be used by tools that support go build and...

@akshayjshah We've made some progress. The `golang.org/x/tools/go/packages` API is nearing completion. Our team has migrated a few tools to use it already, but the effort is ongoing. If you set...

@akshayjshah Sure, it's at https://github.com/jayconrod/rules_go/tree/dev-gopackagesdriver if you'd like to take a look. As I said, it's very rough right now.

@pierreis Sorry, no updates since my last comment. I'm still planning to work on this this quarter. There are a lot of things going on, but this is one of...

Generated .pb.go files are now available in the `go_generated_srcs` output group since #1827. Leaving this issue open though since it's not documented yet.

A driver is still planned, but I don't have any update to share yet. Implementation-wise, the data will be produced by the builder and accessed through an output group (but...

@robbertvanginkel I'm probably not going to keep most of the code on that branch. I don't think gathering information through separate actions via an aspect will be fast enough, and...