Google Python Style Guide
Decision: Use import x for importing packages and modules. Use from x import y where x is the package prefix and y is the module name 3 with no prefix. Use from x import y as z if two modules named relative names in imports. Even if the module is in the same package, use the full package name. This helps prevent unintentionally importing a package twice. Packages link Import each module using the full harder to deploy code because you have to replicate the package hierarchy. Decision: All new code should import each module by its full package name. Imports should be as follows: # Reference in code0 码力 | 30 页 | 94.81 KB | 1 年前303 Experiments, Reproducibility, and Projects - Introduction to Scientific Writing WS2021/22
0.265 M/sec (50.00%) 1016330404 LLC-load-misses # 30.11% of all LL-cache hits (50.00%) 152.096000108 seconds time elapsed 12052.466691000 seconds user 674.704421000 seconds Flags E.g., Understanding Java JIT compilation -XX:+PrintCompilation E.g., Understanding HW Cache Hierarchy (L1i 32KB) -XX:-DontCompileHugeMethods Presentation – Result Interpretation [Matthias Technology, WS 2021/22 SIGMOD Reproducibility Process Overview Accepted papers can submit package, verified by committee ACM Results Replicated / ACM Artifacts Available labels Most Reproducible0 码力 | 31 页 | 1.38 MB | 1 年前301 Structure of Scientific Papers - Introduction to Scientific Writing WS2021/22
compression dedicated sampling schemes and estimators Initially slow compressed operations cache-conscious operations, selected operations with better asymptotic behavior Structure of Scientific directly on the compressed representations. We contribute effective column compression schemes, cache-conscious operations, and an efficient sampling-based compression algorithm. Our experiments show SIGMOD 2006 #16.3 Marcin 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 Jasny0 码力 | 36 页 | 1.12 MB | 1 年前3Google Java Style Guide
structure A source file consists of, in order: 1. License or copyright information, if present 2. Package statement 3. Import statements 4. Exactly one top-level class Exactly one blank line separates each in a file, it 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 (for example, a long URL in Javadoc, or a long JSNI method reference). 2. package and import statements (see Sections 3.2 Package statement and 3.3 Import statements). 3. Command lines in a comment that0 码力 | 19 页 | 84.76 KB | 1 年前3Google C++ Style Guide
size. On modern processors smaller code usually runs faster due to better use of the instruction cache. A decent rule of thumb is to not inline a function if it is more than 10 lines long. Beware of destructors false, nullptr); versus: ProductOptions options; options.set_precision_decimals(7); options.set_use_cache(ProductOptions::kDontUseCache); const DecimalNumber product = CalculateProduct(values, options, /0 码力 | 83 页 | 238.71 KB | 1 年前3
共 5 条
- 1