Development strategies: You've written a library - now what?
summary
Library maintenance focuses on concrete practices: keep documentation and examples for getting started, run unit tests on every change with continuous integration, use static tools like clang-tidy to catch swapped or oddly-converted arguments, and run sanitizers and fuzzers such as OSS-Fuzz to find memory and crash bugs. A real fix sequence shows this works: a multimap clear missed noexcept, tests are added across containers, CI flags the failure, adding noexcept passes tests. Regression prevention and automated tooling materially reduce fear-based edits.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:28Documentation
- 6:12Tests
- 8:50Expected failure tests
- 15:43Boost documentation
- 16:58Test documentation
- 18:13Test suites
- 23:53Practice doesnt make perfect
- 28:28Compilers
- 32:28Static analyzers
- 35:48Dynamic analyzers
- 41:21Users
- 42:26Thank you
- 44:23Example
- 49:42Field experience
- 50:23Managing change
- 51:17Benefits and costs
- 54:57Conclusions
- 55:45Listen to users
- 56:34Have a release
related talks
01h 19mNavigating the development and evolution of a library
58mMaking Libraries Consumable for Non-C++ Developers
31mTips for Library Development (from a Startup Developer)
30mTips for Library Development (from a Startup Developer)
58mResponsibly Abandoning Open Source Projects
47mAdventures with C++ Legacy Codebases: Tales of Incremental Improvement
54mPractical Advice for Maintaining and Migrating Working Code
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future