commit | 12d413b5fee822442980ff3dcef2fe73ed576246 | [log] [tgz] |
---|---|---|
author | brandjon <brandjon@google.com> | Fri May 01 15:19:37 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri May 01 15:21:05 2020 -0700 |
tree | f76f2c2d911df0b691475449cccff8aa44f20af4 | |
parent | d75a48853dc94622fa84ba154be0ff8637a3629f [diff] |
Add comment advising against trying to create new attribute types This clarification was requested by a teammate who was looking into reasons not to define a new type, Dict<String, Union<String, Dict<String, String>>>. I wanted to put a little extra pressure against these kinds of ad hoc extensions. Ideally, there would be no new ad hoc attribute types unless they could be very clearly described and served a pressing need. If we find ourselves greenlighting many more types, we should consider replacing the whole attribute mechanism with something more generic, but I don't see that happening anytime soon. RELNOTES: None PiperOrigin-RevId: 309483549
{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