cases to fail • Verify that new code passes its own test cases • Practice defensive programming • Comments • It's much easier to find defects in modular, well-designed code with well-written and extensive with print statements • In more complex systems, take advantage of existing logging facilities • Comments • Great way to stay "on the path" when developing new code • An easy first step in narrowing down ) • Call tracers and domain-specific diagnostic tools (strace, wireshark, SQL analyzers...) • Comments • Very powerful tools for deterministic problems • Not always useful for non-deterministic problems

CppCon 2023 - Finding Your Codebases C++ RootsDocumentation Changes • Source Control • Headers & Comments • External Documentation • Documentation Requirements 27 of 45 CppCon 2023 - Finding Your Codebases 29 of 45 CppCon 2023 - Finding Your Codebases C++ RootsANSI C Compiled with a C++ Compiler • C++ Comments • Less typedefs for structs 30 of 45 CppCon 2023 - Finding Your Codebases C++ RootsPre C++11 • the past (comments) • Increases confusion • Understand what you are documenting so it makes sense • Don’t just read the code, restate it and hope for the best • Document with your comments (commit messages)

freebsd.org/cgi/man.cgi?query=fail ● Define failpoints by comments ○ gofail enable converts comments to code ○ gofail disable converts code to comments Gofail in TiDB func (txn *tikvTxn) Commit(ctx context will use the same failpoint ● No tools to enable and disable the failpoint automatically ● Code in comments can’t be analyzed by static analysis tools https://github.com/pingcap/failpoint The ideal form

Entry(tornado.web.UIModule): def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", entry=entry, show_comments=show_comments) Tell Tornado to use uimodules.py using the ui_modules in entries %} {% module Entry(entry) %} {% end %} and entry.html: {% module Entry(entry, show_comments=True) %} Modules can include custom CSS and JavaScript functions by overriding the embedded_css margin-bottom: 1em; }" def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", show_comments=show_comments) Module CSS and JavaScript will be included once no

○ careers@istraresearch.com ● Always happy to learn and explore ○ Please - ask questions, make comments 2 Slidesroi.barkan@gmail.com Outline ● Libraries ○ What ○ Why ○ How ● Ranges ○ Introduction novel ways ● “Go catch rabbits” ● Thank you !! ○ Questions and comments are welcome ○ Thanks to Bryce Lelbach for review and comments 27 Slides

UIModule): def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", entry=entry, show_comments=show_comments) Tell Tornado to use uimodules.py using entries %} {% module Entry(entry) %} {% end %} and entry.html: {% module Entry(entry, show_comments=True) %} Modules can include custom CSS and JavaScript functions by overriding the embedded_css margin-bottom: 1em; }" def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", show_comments=show_comments) Module CSS and JavaScript will be included

Transaction-Based Locking Strategy for ContainersCopyright © 2020 Bob Steagall K E W B C O M P U T I N G Some Comments • These tools operate upon containers and with elements, but don’t require changing the containers Locking Strategy for Containers 139Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Some Comments • So far, only std::vector has been used • The maximum number of elements is pre-allocated and Locking Strategy for Containers 140Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Some Comments • Some threads could starve • Transactions might become stale • Other container types may be

describing the feature, its usage and potentially backward incompatibilities. inline documentation (comments and docstrings) in the critical areas of the code explaining the behaviour appropriate test coverage and benefits. Bugs To be accepted, proposed bug fixes should have at least: inline documentation (comments and docstrings) in the critical areas of the code explaining the behaviour at least 1 regression valuable feedback and will be taken seriously. Formal approval Formal approval means “OK to merge” comments, following review, from at least one member of the core team who has expertise in the relevant areas

describing the feature, its usage and potentially backward incompatibilities. inline documentation (comments and docstrings) in the critical areas of the code explaining the behaviour appropriate test coverage and benefits. Bugs To be accepted, proposed bug fixes should have at least: inline documentation (comments and docstrings) in the critical areas of the code explaining the behaviour at least 1 regression valuable feedback and will be taken seriously. Formal approval Formal approval means “OK to merge” comments, following review, from at least one member of the core team who has expertise in the relevant areas

describing the feature, its usage and potentially backward incompatibilities. • inline documentation (comments and docstrings) in the critical areas of the code explaining the behaviour • appropriate test coverage benefits. Bugs To be accepted, proposed bug fixes should have at least: • inline documentation (comments and docstrings) in the critical areas of the code explaining the behaviour • at least 1 regression 183 django cms Documentation, Release 3.9.0 Formal approval Formal approval means “OK to merge” comments, following review, from at least one member of the core team who has expertise in the relevant areas