CppCon 2015: Andrei Alexandrescu “std::allocator...”
CppCon · 6 位 HN 用户推荐 · 2017–2020
It's not exactly roses in C++ either of course. You can do better than the standard library facilities. Andrei Alexandrescu gave a great, entertaining, and technically elegant talk on memory allocation in C and C++ at Cppcon 2015 that is well worth watching [link]
— nly, 2017Generally speaking many C++ game engines avoid the STL stuff and reimplement their own more predictable containers, often with custom allocation schemes. The engine at the last game company i worked at, for example, had its own containers and memory allocator and allowed you to define the allocation category and pool per allocator and per object class (so, e.g., dynamic strings would be isolated t
— badsectoracula, 2017This article highlight the value of "design-by-introspection" applied to a particular problem space: [link] This talk present a concrete example of such: [link] (mind bending stuff)
— p0nce, 2018Andrei Alexandrescu had a great talk[0] on allocators and this convinced me that if you really care about allocator performance[1] what you need is a tunable and composable system. The whole idea of how and when (runtime/compile-time) to choose the appropriate allocator is also interesting. [0] [link]
— Quekid5, 2019Note that this talk is about a std::allocator-like type, potentially on top of one of malloc/jemalloc/etc. [link]
— favorited, 2020Every time I hear someone talking about writing a memory allocator, it always reminds me of the brilliant CppCon 2015 talk by Andrei Alexandrescu about how he wrote an modular allocator library that can be built up in pieces to make whatever you like. [link]
— jiggawatts, 2020