CppCon 2015: Andrei Alexandrescu “Declarative Control Flow"

What people said

uep · 2018-02 · Recommendation

Andrei Alexandrescu has a fun talk about implementing scope_exit using a new C++17 function: std::uncaught_exceptions (which is a tweak to std::uncaught_exception). Fundamentally, it doesn't really solve the destructor throwing exceptions issue though. [VIDEO]

Read the original HN comment ↗

Ace17 · 2016-07 · Recommendation

Google is an example that writing production code that doesn't use exceptions is possible, not that this is the right thing to do. They said that their decision was primarily legacy-motivated (in short, they were fearing that introducing exceptions in a non-RAII codebase would lead us to a long period of instability). I'll add that in some situations (e.g when freeing resources) the control flow gets very convoluted, and you don't want to deal with directly. See: Andrei Alexandrescu - Declarative Control Flow ( [VIDEO] )

Read the original HN comment ↗

einpoklum · 2022-10 · Reference

A count of the number of exceptions in-flight was added, replacing the boolean indication of whether an exception is in-flight. This allows the scope guard construct proposed by Andrei Alexandrescu to distinguish between a scope being left on success and on an exception being thrown. YouTube video about scope guard: [VIDEO] Description of the change to the standard: [LINK]

Read the original HN comment ↗