rule may be waived (some can be), and what sort of argument or alternative would be necessary to change a rule in the guide. The goals of the style guide as we currently see them are as follows: 1 Style declarations can hide a dependency, allowing user code to skip necessary recompilation when headers change. • A forward declaration may be broken by subsequent changes to the library. Forward declarations declaration or a full #include is needed. Replacing an #include with a forward declaration can silently change the meaning of code: // b.h: struct B {}; struct D : B {}; // good_user.cc: #include "b.h" void

multiple spaces are allowed, but not required. 7. Between the type and variable of a declaration: List list 8. Optional just inside both braces of an array initializer 8 • new int[] {5, 6} and new int[] readability, but it creates problems for future mainte- nance. Consider a future change that needs to touch just one line. This change may leave the formerly-pleasing formatting mangled, and that is allowed. More whitespace on nearby lines as well, possibly triggering a cascading series of reformattings. That one-line change now has a “blast radius.” This can at worst result in pointless busywork, but at best it still corrupts

Language Rules Lint Imports Packages Exceptions Global variables Nested/Local/Inner Classes and Functions List Comprehensions Default Iterators and Operators Generators Lambda Functions Conditional Expressions document. Background Python is the main scripting language used at Google. This style guide is a list of dos and don’ts for Python programs. To help you format code correctly, we’ve created a settings that we can easily search for suppres- sions and revisit them. You can get a list of pylint warnings by doing pylint --list-msgs. To get more information on a particular message, use pylint --help-msg=C6409

limit range to make you look good If there are multiple relevant parameters, show them all For log-scale you can’t start at 0 [J. Sommer, M. Boehm, A. V. Evfimievski, B. Reinwald, P. J. Haas: MNC:  Team  1-4 person teams (w/ clearly separated responsibilities)  Project  Pick from a given list of papers / groups of papers  #1 Write short summary paper (#pages = 2 * team-size, written in LaTeX sigconf, PDF)  #2 Prepare and present talk on paper summary (7min + 3min Q&A)  Timeline  Oct 28: List of projects proposals, feel free to bring your own, or ask for extended proposals (e.g., ML systems

Never copy figures or text from other peoples work and claim its yours (slight rewording does not change that)  For archival scientific publications, there is a high chance it will be detected Scientific SIGMOD/PVDLB: 12 pages + unlimited references  ICDE: 12 pages incl. references  #1 Avoid Cheating  Don’t change the template, fonts, or margins (at least not too excessively)  Condensing more text into the paper

 Team  1-4 person teams (w/ clearly separated responsibilities)  Project  Pick from a given list of papers / groups of papers  #1 Write short summary paper (#pages = 2 * team-size, written in LaTeX sigconf, PDF)  #2 Prepare and present talk on paper summary (7min + 3min Q&A)  Timeline  Today: List of projects proposals, feel free to bring your own  Nov 11: project selection via email to m.boehm@tugraz Introduction and Overview Matthias Boehm, Graz University of Technology, WS 2020/21 Title and Authors  List of Authors  #1 by contribution (main, …, advisor)  #2 by last name  Title  Descriptive yet

"Frequency (count of campaignids)") 5 Function Definitions and Calls Function definitions should first list arguments without default values, followed by those with default values. In both function definitions function definition line. These comments should consist of a one-sentence description of the function; a list of the function’s arguments, denoted by Args:, with a description of each (including the data type);