Google C++ Style Guide Google C++ Style Guide Background C++ is one of the main development languages used by many of Google’s open- source projects. As every C++ programmer knows, the language has describing in detail the dos and don’ts of writing C++ code. These rules exist to keep the code base manageable while still allowing coders to use C++ language features produc- tively. Style, also known known as readability, is what we call the conventions that govern our C++ code. The term Style is a bit of a misnomer, since these conventions cover far more than just source file formatting. Most open-source

Language. PVLDB 7(10) 2014  #15.6 Thomas Neumann: Efficiently Compiling Efficient Query Plans for Modern Hardware. Proc. VLDB Endow. 4(9) 2011 Paper Project Proposals 35 706.015 Introduction to Scientific Zukowski, Sándor Héman, Niels Nes, Peter A. Boncz: Super-Scalar RAM-CPU Cache Compression. ICDE 2006  Modern Hardware  #17.1 Lasse Thostrup, Jan Skrzypczak, Matthias Jasny, Tobias Ziegler, Carsten Binnig: Memory. SIGMOD 2016  #17.4 Changkyu Kim et al.: FAST: fast architecture sensitive tree search on modern CPUs and GPUs. SIGMOD 2010  #17.5 René Müller, Jens Teubner, Gustavo Alonso: Data Processing on

S4 objects or methods. A primary justification for an S4 object would be to use objects directly in C++ code. A primary justification for an S4 generic/method would be to dispatch on two arguments. Avoid

symbol. (Note that this is not the same practice used in Google style for other languages, such as C++ and JavaScript.) • This also applies to the following “operator-like” symbols: the dot separator (

easier to read and less error-prone. In most cases, they’re also faster. Cons: May look strange to C/C++ developers. Decision: Use the “implicit” false if at all possible, e.g., if foo: rather than if foo