To Err is Human - Robust Error Handling in C++26
summary
C++23 and C++26 additions get used: std::expected for return-value error flow, contracts for configurable pre/post checks, and library hardening to turn STL preconditions into runtime reports. The system sends a suspended-process mini‑dump to a backend that symbolicates stacks, groups failures by function-offset, and correlates loaded libraries; asserts stay enabled and reports are throttled. Focus is on checking every API call, keeping error paths small, and shipping targeted workarounds when bugs are reproducible.
AI-written summary · about
chapters (10)
- 0:00Robust error handling intro
- 3:40C-style error limits
- 7:13C++ exceptions pros/cons
- 11:30std::expected in C++26
- 16:50Contracts for invariants
- 24:11Library hardening in C++26
- 28:29Error handling best practices
- 36:40Error categorization
- 41:34Automated error reporting
- 45:00Q&A
related talks
44mError handling in C++: as easy as "use exceptions"?
01h 29mC++ Error Handling
44mA Practical Approach to Error Handling
01h 03m“What Could Possibly Go Wrong?: A Tale of Expectations and Exceptions”
01h 04mKEYNOTE: De-fragmenting C++: Making exceptions more affordable and usable
01h 33mHow C++23 Changes the Way We Write Code
53mThe Dawn Of A New Error
01h 02mBack to Basics: Exception Handling and Exception Safety