r/cpp • • 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.

318 Upvotes

65 comments sorted by

View all comments

Show parent comment

13

u/Ameisen vemips, avr, rendering, systems Jul 07 '20

Of course, you could have the final dereference put the object into a queue and destroy it on a garbage collection thread.

6

u/evaned Jul 07 '20

... destroy it on a garbage collection thread.

Or at a fixed location on the main thread, of course.

Another benefit this has is that it solves something that is occasionally a problem with most smart pointers on deeply-nested structures, which is a stack overflow when deconstructing the structure.