CppCon 2016: Herb Sutter “Leak-Freedom in C++... By Default.”

Why HN readers recommended it

HN cites it in memory management debates for its treatment of reference counting problems, destructor stack overflows and deferred pointers.

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++ memory management

Format

talk

Level

advanced

HN recommenders in dataset

2

HN mentions in dataset

20

Recommendation years in dataset

2016–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.

• Check all of Herb Sutter's CppCon videos from 2015-2016, especially this one: [VIDEO] He does a great job of walking through the thought process of deciding which of the options makes sense in different situations.

• Herb Sutter gave a really great talk on this: [VIDEO] He has 3 guidelines: 1. Prefer scoped lifetimes by default (local members) 2. Else prefer unique_ptr and containers 3. Else consider shared_ptr His whole talk gives examples that show the flexibility of unique_ptr and how …

• Reference counting isn't deterministic in the presence of large complex data structures. You will know when memory gets deleted, but not how long it will take, nor how much stack space the destructors will require to run. Enjoy Herb Sutter's "Leak-Freedom in C++... By Default." …