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, if present If license or copyright information belongs here. 3.2 Package statement The package statement is not line-wrapped. The column limit (Section 4.4, Column limit: 100) does not apply to package statements. 3.3 Import statements 3.3.1 No wildcard are not used. 3.3.2 No line-wrapping Import statements are not line-wrapped. The column limit (Section 4.4, Column limit: 100) does not apply to import statements. 3 3.3.3 Ordering and spacing Imports

base/basictypes_test.cc and base/basictypes.h), but may sometimes be in different directories too. Within each section the includes should be ordered alphabetically. Note that older code might not conform to this rule Classes Classes are the fundamental unit of code in C++. Naturally, we use them extensively. This section lists the main dos and don’ts you should follow when writing a class. Doing Work in Constructors support copy/move operations on your type, explicitly disable them using = delete in the public: section. 17 Structs vs. Classes Use a struct only for passive objects that carry data; everything else

of the indentation of the elements in the line continuation examples above; see the indentation section for explanation. Parentheses link￿ Use parentheses sparingly. Do not use them in return statements continuation, you should align wrapped elements either vertically, as per the examples in the line length section; or using a hanging indent of 4 spaces, in which case there should be no argument on the first line by the project (for example, Apache 2.0, BSD, LGPL, GPL) Functions and Methods As used in this section “function” applies to methods, function, and generators. A function must have a docstring, unless

Prefer primary sources Scientific Writing In this section, we provide the background and motivation for compressed linear algebra. In this section, the background and motivation for compressed linear 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 Writing Figure~\ref{fig:exp1} Equation~\eqref{eq:e1} published work, following the guidelines in the Anonymity Requirements for Double-Blind Reviewing section below. Scientific Writing 25 706.015 Introduction to Scientific Writing – 02 Scientific Reading

Matthias Boehm, Graz University of Technology, WS 2020/21 Related Work  Purpose of a “Related Work”-Section  Not a mandatory task or to show you know the field  Put you work in context of related areas related work  Crisp separation from existing work (what are the differences)  Placement  Section 2 or Section n-1  Throughout the paper  Give Credit  Cite broadly, give credit to inspiring ideas

calls (for shared library rou- tines). Function Documentation Functions should contain a comments section immediately below the function definition line. These comments should consist of a one-sentence description

 Create value for others (compare, reuse, understand, extend)  EU Projects: Mandatory proposal section & deliverable on RDM plan  RDM @ TU Graz: https://www.tugraz.at/sites/rdm/home/  Toni Ross-Hellauer