Google C++ Style Guidehave been made. If you understand what goals each rule is serving, it should be clearer to everyone when a rule may be waived (some can be), and what sort of argument or alternative would be necessary to reader, not the writer Our codebase (and most individ- ual components submitted to it) is expected to continue for quite some time. As a result, more time will be spent reading most of our code than writing debugging code in our codebase rather than ease when writing said code. “Leave a trace for the reader” is a particularly common sub-point of this principle: When some- thing surprising or unusual is happening0 码力 | 83 页 | 238.71 KB | 1 年前3
Google Python Style GuideFunctions List Comprehensions Default Iterators and Operators Generators Lambda Functions Conditional Expressions Default Argument Values Properties True/False evaluations Deprecated Language Features Lexical 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 symbolic name, add is not cluttered by error- handling code. It also allows the control flow to skip multiple frames when a certain condition occurs, e.g., returning from N nested functions in one step instead of having0 码力 | 30 页 | 94.81 KB | 1 年前3
Google Java Style Guideliterals and comments are strongly dis- couraged. Tip: In the Unicode escape case, and occasionally even when actual Unicode characters are used, an explanatory comment can be very helpful. Examples: Example “chronological by date added” ordering, which is not a logical ordering. 3.4.2.1 Overloads: never split When a class has multiple constructors, or multiple methods with the same name, these appear sequentially Braces are used where optional Braces are used with if, else, for, do and while statements, even when the body is empty or contains only a single statement. 4.1.2 Nonempty blocks: K & R style Braces0 码力 | 19 页 | 84.76 KB | 1 年前3
Google's R Style GuideFunctions: errors should be raised using stop() 3. Objects and Methods: 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 CalculateAvgClicks BAD: calculate_avg_clicks , calculateAvgClicks Make function names verbs. Exception: When creating a classed object, the function name (constructor) and class should match (e.g., lm). • kConstantName Indentation When indenting your code, use two spaces. Never use tabs or mix tabs and spaces. Exception: When a line break occurs inside parentheses, align the wrapped line with the first character inside the parenthesis0 码力 | 8 页 | 47.42 KB | 1 年前3
03 Experiments, Reproducibility, and Projects - Introduction to Scientific Writing WS2021/22Evfimievski, B. Reinwald, P. J. Haas: MNC: Structure- Exploiting Sparsity Estimation for Matrix Expressions. SIGMOD 2019] 15 706.015 Introduction to Scientific Writing – 03 Experiments & Reproducibility Metadata and data retrievable via open, free and universal comm protocols Metadata accessible even when data no longer available #3 Interoperable Metadata and data use a formal, accessible, and broadly Evfimievski, B. Reinwald, P. J. Haas: MNC: Structure- Exploiting Sparsity Estimation for Matrix Expressions. SIGMOD 2019] 27 706.015 Introduction to Scientific Writing – 03 Experiments & Reproducibility0 码力 | 31 页 | 1.38 MB | 1 年前3
02 Scientific Reading and Writing - Introduction to Scientific Writing WS2021/22sublists Exclamations Avoid exclamation marks! Never use more than one!! Scientific Writing When using disk[,] tree algorithms were found to be particularly poor. We use index structures like b-trees0 码力 | 26 页 | 613.57 KB | 1 年前3
共 6 条
- 1













