-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
Labels:None
-
Service Arch
-
Service Arch 2022-05-02
At least twice, I have spent minutes or hours debugging a crash at a line like this:
auto& readConcernArgs = ReadConcernArgs::get(opCtx);
Eventually, I will realize that my code crashes because opCtx is nullptr. If this is a common mistake, we could speed up debugging it by asserting in Decorable::Decorator::operator () that the pointer to the decorated object is not null