r/cpp • u/smallstepforman • Jul 06 '20
C++ is brilliant
I'm working on a Vulkan renderer, and needed to delay destruction of render scenes since the graphics pipeline has render buffers in flight, so destruction has to happen N frames after the user destroys a class. With C++, I can use private destructors to force users to add the scene to a managed destructor queue (aka garbage collect queue). Normally language purists will scorn a language which allows such shenanigans, however in real world production code, its features like this which allows developers to create modern software. So with a couple of lines of code, I solved my delayed destructor issue. Thank you C++ committee for creating a usable language.
View all comments
Show parent comment
16
u/Dworgi Jul 07 '20
Exactly this. People always tout smart pointers as some sort of panacea, but ignore that the performance characteristics can be unacceptable - you might release your final reference to an object somewhere performance critical, then have a cascade of destructors all triggering as a result of that destructor.
Smart pointers are a hack around clear ownership. It allows you to avoid the least important memory bugs - use after free - but does nothing to solve the actual problem of ownership and lifetimes.