De-fragmenting C++: Making Exceptions and RTTI More Affordable and Usable - Herb Sutter CppCon 2019

Why HN readers recommended it

Pointed to whenever C++ exception overhead, bans on exceptions or error-handling alternatives come up.

This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.

Video & recommendation details

Creator / channel

CppCon

Topic

c++ exceptions

Format

talk

Level

advanced

HN recommenders in dataset

3

HN mentions in dataset

9

Recommendation years in dataset

2020–2025

These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.

From the original HN conversations

Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.

• Quite an improvement. However, i feel like that the tweet also displays the (sometimes emotional) feelings toward exceptions that a large part of the C++ community has. Herb Sutter made an excellent presentation about this "fragmentation" of the community and steps towards fixing this split: …

• If you want to see Herb Sutter's take on exceptions (and RTTI), I can really recommend this talk where he explores his Result-esque (like in Rust) solution that he wrote a paper about and proposes for standardisation: [VIDEO]

• Wow: C++ > Garbage collection was never added into C++. Manual memory management is extremely error prone. C++ has memory management simplification: reference couting via shared_ptr/unique_ptr. The trade-offs are different, but in C++ manually managing memory is not necessary unless you have a good reason. …