Скачать или смотреть Phil Nash - Modern C++ Error Handling

We’ve had exceptions in C++ since before the first standard. C++17 introduced std::optional and C++23 std::expected (along with the so-called Monadic Operations for both types).

What should we use and when? Meanwhile we still have older approaches, such as boolean or error code returns, as well as global or thread local error status or pointer or reference arguments. Do these still have a place? And where does assert fit in? And the (hopefully) upcoming contracts? Perhaps more importantly, once we’ve examined all the trade-offs, can we defer any of those decisions to when we are best positioned to commit to them?

Erroneous conditions can have a big impact on your code’s safety and security, so error handling shouldn’t just be left to the “exercise left for the reader” in the books we used to read. Let’s get this all straight.

Phil Nash

Phil is the original author of the C++ test framework, Catch2. He's also a member of the ISO C++ standards committee, organiser of C++ London, C++ on Sea, C++ Online and ACCU - as well as co-host and producer of CppCast.

He's previously worked in Finance, Mobile and developer tools but has recently become fully independent, offering training in TDD and various C++ topics.

More generally he's an advocate for good testing practices, TDD and using the type system and functional techniques to reduce complexity and increase correctness.