instantiated for all relevant sets of template arguments, or that is a private implementation detail of a class, is allowed to be defined in the one and only .cc file that instantiates the template. There are where possible. Just #include the headers you need. A “forward declaration” is a declaration of a class, function, or template without an associated definition. • Forward declarations can save compile declared in a header file, always #include that header. • When using a class template, prefer to #include its header file. Please see Names and Order of Includes for rules about when to #include a header.

Terminology notes In this document, unless otherwise clarified: 1. The term class is used inclusively to mean an “ordinary” class, enum class, interface or annotation type (@interface). 2. The term comment always basics 2.1 File name The source file name consists of the case-sensitive name of the top-level class it contains (of which there is exactly one), plus the .java extension. 2.2 File encoding: UTF-8 copyright information, if present 2. Package statement 3. Import statements 4. Exactly one top-level class Exactly one blank line separates each section that is present. 3.1 License or copyright information

identified by a alphanumeric code (C0112) and a sym- bolic name (empty-docstring). Prefer the symbolic names in new code or when updating existing code. If the reason for the suppression is not clear from the argument or prefixing the argument name with ‘unused_’. In situations where changing the argument names is infeasible, you can mention them at the beginning of the function. For example: def foo(a, unused_b consistent way; x.Obj says that object Obj is defined in module x. Cons: Module names can still collide. Some module names are inconveniently long. Decision: Use import x for importing packages and modules

designed in collaboration with the entire R user community at Google. Summary: R Style Rules 1. File Names: end in .R 2. Identifiers: variable.name (or variableName), FunctionName, kConstantName 3. Line Length: avoid S4 objects and methods when possible; never mix S3 and S4 1 Notation and Naming File Names File names should end in .R and, of course, be meaningful. GOOD: predict_ad_revenue.R BAD: foo.R Identifiers conventions. The preferred form for variable names is all lower case letters and words separated with dots (variable.name), but variableName is also accepted; function names have initial capital letters and no

if applicable use mix of different plot types and tables  Consistency: use consistent colors and names for same baselines  Labeling  Make the plots self-contained  Simplifies skimming and avoids join Write short summary paper (#pages = 2 * team-size, written in LaTeX, ACM acmart template, document-class sigconf, PDF)  #2 Prepare and present talk on paper summary (7min + 3min Q&A)  Timeline  Oct

Titles and Names  Titles: capitalize meaning-carrying words  Names: capitalize, e.g., Bayesian, Euclidean  References like Figure 1, Table 2, Section 3, Chapter 4, Equation 5 are names as well Scientific

Write short summary paper (#pages = 2 * team-size, written in LaTeX, ACM acmart template, document-class sigconf, PDF)  #2 Prepare and present talk on paper summary (7min + 3min Q&A)  Timeline  Today: #17.3 Ismail Oukid et al.: FPTree: A Hybrid SCM-DRAM Persistent and Concurrent B-Tree for Storage Class Memory. SIGMOD 2016  #17.4 Changkyu Kim et al.: FAST: fast architecture sensitive tree search on