Post-mortem of a long-standing bug in video Game Path Of Exile, which was caused by a stale pointer

1. Qt

   1 28 2,632 10.0 C++

   Qt Base (Core, Gui, Widgets, Network, ...)

   

   Interestingly Qt has QPointer which nulls itself out when the target T is deleted. It's convenient when I want weak references to GUI objects (though you have to be careful to check for its presence after every time you call code which could possibly delete it, I usually call it QPointer maybe_foo). However, from my brief look at the source (link), it's implemented in terms of qsharedpointer.h-> qsharedpointer_impl.h and QtSharedPointer (not sure how it works, but there's probably overhead going on). I wonder how it works, and compares to generational indexes or Vale's generational references (link).

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. OpenSceneGraph

   2 12 3,328 0.0 C++

   OpenSceneGraph git repository

   

   I started in 2001 with OpenSceneGraph which made extensive use of intrusive pointers. This was 10 years before C++11 note. That codebase continues to be relevant and as performing as ever.

Suggest a related project