Placement new and assignment of class with const member

by

There is nothing that makes the shown code snippet inherently UB. However, it is almost certain UB will follow immediately under any normal usage.

From [basic.life]/8 (emphasis mine)

If, after the lifetime of an object has ended and before the storage which the object occupied is reused or released, a new object is created at the storage location which the original object occupied, a pointer that pointed to the original object, a reference that referred to the original object, or the name of the original object will automatically refer to the new object and, once the lifetime of the new object has started, can be used to manipulate the new object, if:

  • the storage for the new object exactly overlays the storage location which the original object occupied, and

  • the new object is of the same type as the original object (ignoring the top-level cv-qualifiers), and

  • the type of the original object is not const-qualified, and, if a class type, does not contain any non-static data member whose type is const-qualified or a reference type, and

  • the original object was a most derived object of type T and the new object is a most derived object of type T (that is, they are not base class subobjects).

Since there is a const member in s, using the original variable after a call to operator= will be UB.

s var{42};
var = s{420};         // OK
do_something(var.id); // UB! Reuses s through original name
do_something(std::launder(&var)->id);  // OK, this is what launder is used for

More Related Contents:

  1. Is there a (semantic) difference between the return value of placement new and the casted value of its operand?
  2. Do I really need to implement user-provided constructor for const objects?
  3. treating memory returned by operator new(sizeof(T) * N) as an array
  4. Why does left shift operation invoke Undefined Behaviour when the left side operand has negative value?
  5. What is meant with “const” at end of function declaration? [duplicate]
  6. int vs const int& [closed]
  7. Is stateful metaprogramming ill-formed (yet)?
  8. Is it safe to push_back an element from the same vector?
  9. Deleted default constructor. Objects can still be created… sometimes
  10. Why catch an exception as reference-to-const?
  11. Order of evaluation of assignment statement in C++
  12. Why should the assignment operator return a reference to the object?
  13. Why cannot a non-member function be used for overloading the assignment operator?
  14. Calling a const function rather than its non-const version
  15. Why use a const member function?
  16. Casting double array to a struct of doubles
  17. What are top-level const qualifiers?
  18. Pointer to array with const qualifier in C & C++
  19. What is the value category of the operands of C++ operators when unspecified?
  20. How C++ placement new works?
  21. Are pointer variables just integers with some operators or are they “symbolic”?
  22. Is left-shifting (
  23. How to avoid code duplication implementing const and non-const iterators?
  24. Why isn’t `std::initializer_list` defined as a literal type?
  25. C++: Why is const_cast evil?
  26. What is difference between const and non const key?
  27. Same function with const and without – When and why?
  28. Duplicate const qualifier allowed in C but not in C++?
  29. What standard clause mandates this lvalue-to-rvalue conversion?
  30. Is there const in C?

Leave a Comment