for the 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 transfer of pointer ownership), leaving textual hints for the reader at the point of use is valuable (std::unique_ptr demonstrates the ownership transfer unambiguously at the call site). Be consistent with with a default value, or migrating to a new namespace. • Forward declaring symbols from namespace std:: yields undefined be- havior. • It can be difficult to determine whether a forward declaration or

comment if its name is or begins with expected. The following is a very common idiom for ensuring that the code under test does throw an exception of the expected type, so a comment is unnecessary here here. try { emptyStack.pop(); fail(); } catch (NoSuchElementException expected) { } 6.3 Static members: qualified using class When a reference to a static class member must be qualified, it is qualified

Replicability (aka Repeatability)  Recreate result data and graphs shown in the final paper  Expected: same trend of baseline comparisons, parameter influence  #2 Reproducibility  Verify robustness