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

What people said

shermanyo · 2016-09 · Strong recommendation

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.

Read the original HN comment ↗

pjmlp · 2020-01 · Recommendation

On single core without threading. If you add multi-threading and multi-core, there is lock contention for every single memory access to update the related counter. Additionally, if there is a big data structure in use, reaching zero will trigger a cascade deletion events reaching stop-the-world like effect. Which, depending on how the deletion was implemented, might trigger a stack overflow in very deep structures. Herb Sutter has a very interesting talk about the bad issues of reference counting and how to work around them. CppCon 2016: Herb Sutter “Leak-Freedom in C++... By Default.” [VIDEO] There are multiple ways to optimize reference counting, like deferred counting, cycle collectors and a couple of others, which when you are done with all them, ends up being quite similar to having a tracing GC anyway.

Read the original HN comment ↗

pjmlp · 2019-01 · Recommendation

Herb Sutter has a nice talk about how RAII can cause stack overflows or stop-the-world pauses if used badly. [VIDEO]

Read the original HN comment ↗