| commit | 9d5c0a0eb26ab17d152f0cb8281cbc94e9377776 | [log] [tgz] |
|---|---|---|
| author | laurentlb <laurentlb@google.com> | Tue Jun 13 23:08:06 2017 +0200 |
| committer | Yun Peng <pcloudy@google.com> | Wed Jun 14 13:17:16 2017 +0200 |
| tree | 3225658de8732609fb4aa4f6ed3b2e8344987a55 | |
| parent | e0e0071b6b34594f3d283dfff446d572c24539dd [diff] |
Introduce --incompatible_comprehension_variables_do_not_leak When the flag is activated, variables in list comprehensions do not leak anymore. Even if a variable was defined before the loop, it's not accessible after the loop. This change allows us to detect any breakage and ensures that no user is accessing loop variables after the loop. This will make possible for us to change the behavior and follow Python 3 semantics in the future. RELNOTES: None. PiperOrigin-RevId: 158895514
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.