6 Basics [basic]

6.8 Memory and objects [basic.memobj]

6.8.4 Lifetime [basic.life]

In this subclause, “before” and “after” refer to the “happens before” relation ([intro.multithread]).

The lifetime of an object or reference is a runtime property of the object or reference.

A variable is said to have vacuous initialization if it is default-initialized, no other initialization is performed, and, if it is of class type or a (possibly multidimensional) array thereof, a trivial constructor of that class type is selected for the default-initialization.

The lifetime of an object of type T begins when:

(2.1)
storage with the proper alignment and size for type T is obtained, and
(2.2)
its initialization (if any) is complete (including vacuous initialization) ([dcl.init], [class.base.init]),

except that if the object is a union member or subobject thereof, its lifetime only begins if that union member is the initialized member in the union ([dcl.init.aggr], [class.base.init]), or as described in [class.union], [class.copy.ctor], [class.copy.assign], and [obj.lifetime], and except as described in [allocator.members].

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

(2.3)
if T is a non-class type, the object is destroyed, or
(2.4)
if T is a class type, the destructor call starts, or
(2.5)
the storage which the object occupies is released, or is reused by an object that is not nested within o ([intro.object]).

When evaluating a new-expression, storage is considered reused after it is returned from the allocation function, but before the evaluation of the new-initializer ([expr.new]).

[Example 1: struct S { int m; }; void f() { S x{1}; new(&x) S(x.m); // undefined behavior } — end example]

The lifetime of a reference begins when its initialization is complete.

The lifetime of a reference ends as if it were a scalar object requiring storage.

[Note 1:

[class.base.init] describes the lifetime of base and member subobjects.

— end note]

The properties ascribed to objects and references throughout this document apply for a given object or reference only during its lifetime.

[Note 2:

In particular, before the lifetime of an object starts and after its lifetime ends there are significant restrictions on the use of the object, as described below, in [class.base.init], and in [class.cdtor].

Also, the behavior of an object under construction and destruction can differ from the behavior of an object whose lifetime has started and not ended.

[class.base.init] and [class.cdtor] describe the behavior of an object during its periods of construction and destruction.

— end note]

A program may end the lifetime of an object of class type without invoking the destructor, by reusing or releasing the storage as described above.

[Note 3:

A delete-expression ([expr.delete]) invokes the destructor prior to releasing the storage.

— end note]

In this case, the destructor is not implicitly invoked.

[Note 4:

The correct behavior of a program often depends on the destructor being invoked for each object of class type.

— end note]

Before the lifetime of an object has started but after the storage which the object will occupy has been allocated¹⁶ or after the lifetime of an object has ended and before the storage which the object occupied is reused or released, any pointer that represents the address of the storage location where the object will be or was located may be used but only in limited ways.

For an object under construction or destruction, see [class.cdtor].

Otherwise, such a pointer refers to allocated storage ([basic.stc.dynamic.allocation]), and using the pointer as if the pointer were of type void* is well-defined.

Indirection through such a pointer is permitted but the resulting lvalue may only be used in limited ways, as described below.

The program has undefined behavior if:

(7.1)
the pointer is used as the operand of a delete-expression ([ub:lifetime.outside.pointer.delete]),
(7.2)
the pointer is used to access a non-static data member or call a non-static member function of the object ([ub:lifetime.outside.pointer.member]), or
(7.3)
the pointer is converted ([conv.ptr], [expr.static.cast]) to a pointer to a virtual base class ([ub:lifetime.outside.pointer.virtual]) or to a base class thereof, or
(7.4)
the pointer is used as the operand of a dynamic_cast ([expr.dynamic.cast]) ([ub:lifetime.outside.pointer.dynamic.cast]).

[Example 2: #include <cstdlib> struct B { virtual void f(); void mutate(); virtual ~B(); }; struct D1 : B { void f(); }; struct D2 : B { void f(); }; void B::mutate() { new (this) D2; // reuses storage --- ends the lifetime of *this f(); // undefined behavior ... = this; // OK, this points to valid memory } void g() { void* p = std::malloc(sizeof(D1) + sizeof(D2)); B* pb = new (p) D1; pb->mutate(); *pb; // OK, pb points to valid memory void* q = pb; // OK, pb points to valid memory pb->f(); // undefined behavior: lifetime of *pb has ended } — end example]

Similarly, before the lifetime of an object has started but after the storage which the object will occupy has been allocated or after the lifetime of an object has ended and before the storage which the object occupied is reused or released, any glvalue that refers to the original object may be used but only in limited ways.

For an object under construction or destruction, see [class.cdtor].

Otherwise, such a glvalue refers to allocated storage ([basic.stc.dynamic.allocation]), and using the properties of the glvalue that do not depend on its value is well-defined.

The program has undefined behavior if:

(8.1)
the glvalue is used to access the object ([ub:lifetime.outside.glvalue.access]), or
(8.2)
the glvalue is used to call a non-static member function of the object ([ub:lifetime.outside.glvalue.member]), or
(8.3)
the glvalue is bound to a reference to a virtual base class ([dcl.init.ref]) ([ub:lifetime.outside.glvalue.virtual]), or
(8.4)
the glvalue is used as the operand of a dynamic_cast ([expr.dynamic.cast]) or as the operand of typeid ([ub:lifetime.outside.glvalue.dynamic.cast]).

[Note 5:

Therefore, undefined behavior results if an object that is being constructed in one thread is referenced from another thread without adequate synchronization.

— end note]

An object

o_{1}

is transparently replaceable by an object

o_{2}

if either

(9.1)
$o_{1}$ and $o_{2}$ are complete objects for which:
- (9.1.1)
  $o_{1}$ is not const,
- (9.1.2)
  the storage that $o_{2}$ occupies exactly overlays the storage that $o_{1}$ occupied, and
- (9.1.3)
  $o_{1}$ and $o_{2}$ are of the same type (ignoring the top-level cv-qualifiers), or
(9.2)
$o_{1}$ and $o_{2}$ are corresponding direct subobjects ([intro.object]) for which:
- (9.2.1)
  the complete object of $o_{1}$ is not const or
- (9.2.2)
  $o_{1}$ is a mutable member subobject or a subobject thereof.

After the lifetime of an object has ended and before the storage which the object occupied is reused or released, if a new object is created at the storage location which the original object occupied and the original object was transparently replaceable by the new object, 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.

[Example 3: struct C { int i; void f(); const C& operator=( const C& ); }; const C& C::operator=( const C& other) { if ( this != &other ) { this->~C(); // lifetime of *this ends new (this) C(other); // new object of type C created f(); // well-defined } return *this; } C c1; C c2; c1 = c2; // well-defined c1.f(); // well-defined; c1 refers to a new object of type C — end example]

[Note 6:

If these conditions are not met, a pointer to the new object can be obtained from a pointer that represents the address of its storage by calling std::launder ([ptr.launder]).

— end note]

If a program ends the lifetime of an object of type T with static ([basic.stc.static]), thread ([basic.stc.thread]), or automatic ([basic.stc.auto]) storage duration and if T has a non-trivial destructor,¹⁷ and another object of the original type does not occupy that same storage location when the implicit destructor call takes place, the behavior of the program is undefined ([ub:original.type.implicit.destructor]).

This is true even if the block is exited with an exception.

[Example 4: class T { }; struct B { ~B(); }; void h() { B b; new (&b) T; } // undefined behavior at block exit — end example]

Creating a new object within the storage that a const, complete object with static, thread, or automatic storage duration occupies, or within the storage that such a const object used to occupy before its lifetime ended, results in undefined behavior ([ub:creating.within.const.complete.obj]).

[Example 5: struct B { B(); ~B(); }; const B b; void h() { b.~B(); new (const_cast<B*>(&b)) const B; // undefined behavior } — end example]

16)16)

For example, before the dynamic initialization of an object with static storage duration ([basic.start.dynamic]).

17)17)

That is, an object for which a destructor will be called implicitly—upon exit from the block for an object with automatic storage duration, upon exit from the thread for an object with thread storage duration, or upon exit from the program for an object with static storage duration.