Skip to content

Commit 51d1b68

Browse files
Dawn Perchikzygoloid
authored andcommitted
LWG3005 Destruction order of arrays by make_shared/allocate_shared only recommended?
1 parent 8123d82 commit 51d1b68

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

source/utilities.tex

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9764,7 +9764,8 @@
97649764
\item
97659765
When the lifetime of the object managed by the return value ends, or
97669766
when the initialization of an array element throws an exception,
9767-
the initialized elements should be destroyed in the reverse order of their construction.
9767+
the initialized elements are destroyed in the reverse order
9768+
of their original construction.
97689769
\end{itemize}
97699770
\begin{note}
97709771
These functions will typically allocate more memory than \tcode{sizeof(T)} to

0 commit comments

Comments
 (0)