C++ Standard Library

8 engineers on Hacker News describe using C++ Standard Library first-hand: 2 endorse it, 3 regret it, 1 are mixed.

44%trust
8first-hand users
7in production
endorse 2mixed 1regret 3uses, no opinion

“I barely use the STL; most of that template-heavy junk has been replaced in most of my projects.”

regret · personal · gary_0 · 2024-11-14 · source ↗ · wrong label?

“the performance of my application went out the window, and I had to override all memory allocation related functions”

regret · production · b20000 · 2021-12-09 · source ↗ · wrong label?

“I've been using the STL for 14 years, and only thing I've worked around was std::map”

mixed · production · 14 yr · hermitdev · 2018-12-13 · source ↗ · wrong label?

“No complaints. Actually, I've been using it in several components that are "pure C++" (i.e., no Qt, only STL).”

endorse · production · gusmd · 2017-12-08 · source ↗ · wrong label?

“for our synchronized collections, we switched to std::mutex, which was massively faster.”

endorse · production · asarazan · 2013-05-13 · source ↗ · wrong label?

“I have always ended up building higher-performance custom collections for stuff and found STL with its iterator-instead-of-ranges clunky.”

regret · production · willvarfar · 2012-10-16 · source ↗ · wrong label?

“I made sure the same devirtualization would apply in production too... It was a bit surprising that vtables outperformed std::variant”

neutral · production · vlovich123 · 2021-12-13 · source ↗ · wrong label?

“By 2004 or so we switched the code over the STL and the LLSkipList class was retired”

neutral · production · CoryOndrejka · 2010-03-06 · source ↗ · wrong label?