Closed krlmlr closed 7 years ago
Agreed. NULLing out the pointers would be correct.
Thanks Nigel for #43 - this should eliminate the warning (please feel free to reopen if you still have issues).
As a side note, I'm quite sure this was in fact a false alarm as other internal implementation details ensure these pointers are always initialized. However, it's always good to keep the warnings to a minimum.
Thanks. Agreed that the implementation may have been correct before, but it still feels safer to initialize.
Thanks. Agreed that the implementation may have been correct before, but it still feels safer to initialize.
https://github.com/c42f/tinyformat/blob/46a6d778e7abafa057efc546197603d32719bfc5/tinyformat.h#L490
This confuses Coverity, and also looks unsafe:
Reference: https://github.com/RcppCore/Rcpp/issues/760