To err is human - error handling in C++26
summary
C++26 adds concrete tools used here: std::expected for rich return values, contracts for configurable assertions, and hardened libraries plus stack traces for runtime checks. The workflow checks every API call, classifies failures (critical vs expected), runs an out‑of‑process collector that creates mini‑dumps, uploads and symbolicates them server‑side, and focuses fixes on reproducible field bugs. Uses noexcept, aggressive asserts, retry wrappers (macros) and reporting handlers; the pipeline finds rare environment-only bugs and results in targeted, testable fixes.
AI-written summary · about
chapters (9)
- 0:00Error handling in C++26
- 1:27Error handling in desktop apps
- 6:05C-style error handling limits
- 9:10Exceptions as better tool
- 16:20std::expected simplicity
- 21:18Contracts for runtime checks
- 31:33Practical error handling
- 45:47Error reporting in production
- 59:06Q&A
