Is it OK not to call the destructor on placement new allocated objects?

by

The standard has a rule in section 3.8 [basic.life] that covers this:

A program may end the lifetime of any object by reusing the storage which the object occupies or by explicitly calling the destructor for an object of a class type with a non-trivial destructor. For an object of a class type with a non-trivial destructor, the program is not required to call the destructor explicitly before the storage which the object occupies is reused or released; however, if there is no explicit call to the destructor or if a delete-expression (5.3.5) is not used to release the storage, the destructor shall not be implicitly called and any program that depends on the side effects produced by the destructor has undefined behavior.

Lots of experts are in agreement that “depends on the side effects produced by the destructor” is far too vague to be useful. Many interpret it as a tautology meaning “If the program has undefined behavior when the destructor side effects are not evaluated, then failing to call the destructor causes undefined behavior”. See Observable behavior and undefined behavior — What happens if I don’t call a destructor?

If your type has a trivial destructor (which appears to be the case in your example), then calling it (or failing to call it) has no effect whatsoever — calling a trivial destructor does not even end the life of the object.

The lifetime of an object o of type T ends when:

  • if T is a class type with a non-trivial destructor, the destructor call starts, or
  • the storage which the object occupies is released, or is reused by an object that is not nested within o.

That is, if T doesn’t have a non-trivial destructor, the only way to end the lifetime of object o is to release or reuse its storage.

More Related Contents:

  1. What does "^=" in c++ mean? [duplicate]
  2. How to write this code in simple way?
  3. programming task ask [closed]
  4. How to add a timer in a C++ program [closed]
  5. Unnamed/anonymous namespaces vs. static functions
  6. Multi-character constant warnings
  7. Detecting signed overflow in C/C++
  8. Is there a C pre-processor which eliminates #ifdef blocks based on values defined/undefined?
  9. C++ invoke explicit template constructor
  10. Do I need to manually close an ifstream?
  11. How do you properly use namespaces in C++?
  12. GCC STL bound checking
  13. “:” (colon) in C struct – what does it mean? [duplicate]
  14. Create a directory if it doesn’t exist
  15. Convert Mat to Array/Vector in OpenCV
  16. Why are Python Programs often slower than the Equivalent Program Written in C or C++?
  17. Fast String Hashing Algorithm with low collision rates with 32 bit integer [closed]
  18. Is it safe to `delete this`? [duplicate]
  19. vs. vs. “iostream.h”
  20. boost::asio and Active Object
  21. Why is it not possible to overload class templates?
  22. Converting YUV into BGR or RGB in OpenCV
  23. Is accessing data in the heap faster than from the stack?
  24. How to Setup VS Code For C++ 14 /C ++17
  25. C++ inheritance and function overriding
  26. throw new std::exception vs throw std::exception
  27. Why infinite recursion leads to seg fault
  28. Why does using push_back on a vector declared with size result in a vector of zeros?
  29. virtual function const vs virtual function non-const
  30. Reading files larger than 4GB using c++ stl

Leave a Comment