(This article assumes some familiarity with shared_ptrs in C++.) Imagine the following line of code and comment are in the private area of the definition of a C++ class Foo: // The current Quaffle, always valid shared_ptr<Quaffle> currentQuaffle; Can you spot any dangerous thinking here? If not, that’s okay, but hopefully this article will change … Continue reading shared_ptr_nonnull and the Zen of reducing assumptions
iZotope Tech Blog 