Enable bazel builds without --nocheck_visibility about xla HOT 5 CLOSED

I think the fundamental issue here is that visibility is almost useless outside of a monorepo. We also have to build our integration with TF with --nocheck_visibility (related, bazelbuild/bazel#16767)

from xla.

I think it's still useful to have visibility within each repository, e.g., for internal structuring purposes. The key is that we should open visibility to any public targets that cross repository boundaries.

from xla.

Right, it's nice intra-project but totally breaks across projects. Which is fine in google3 because it's all one "project". I think the concept of visibility groups is useful, but the implementation is totally not set up for a moderately complex constellation of projects

from xla.

Any updates? It's unfortunate to break visibility for all the downstream users and their own internals.

from xla.

As of, ccceb5f, this is resolved.

from xla.