bazel analysis: add verbose assertion for diagnosis of latent NPE bug Add a preconditions check for a null starlark option as a response to http://b/153053875. I couldn't successfully repro the failure so adding this check in here to note the latent bug. The logic here is complicated by aliases - also tried to add some helpful comments along the way for details I have to relearn every time I look at this code. PiperOrigin-RevId: 306705250
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
