Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[utility.requirements,exception.propagation] Clarify the thrown exceptions that have requirements and guarantees imposed LWG3640 #4869

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions source/lib-intro.tex
Original file line number Diff line number Diff line change
Expand Up @@ -1427,6 +1427,8 @@
\ref{hash.requirements} describes the requirements on hash function objects.
\ref{allocator.requirements} describes the requirements on storage
allocators.
\ref{exception.propagation}
describes additional requirements and guarantees when propagating exceptions.

\rSec3[utility.arg.requirements]{Template argument requirements}

Expand Down Expand Up @@ -2218,6 +2220,24 @@
other than \tcode{value_type} are complete types.
\end{itemize}

\rSec3[exception.propagation]{Exception propagation requirements}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not obvious to me that we want to go in this direction, or whether we prefer fixing the individual descriptions to talk about "initialization" and "assignment" more directly instead of choosing wording that allows to ignore some areas of the full-expression under discussion.


\pnum
Some functions defined in the \Cpp{} standard library
impose requirements and guarantees when an exception is thrown from a described evaluation.
Unless stated otherwise,
exceptions thrown due to evaluating the subexpression
that implements the described evaluation
up to the complete evaluation of its enclosing full-expression
also have those requirements and guarantees imposed.
\begin{note}
This includes exceptions thrown as part of
initializing parameters,
evaluating default arguments, and
destroying temporaries (including discarded-value expressions)
\iref{expr.call}.
\end{note}

\rSec2[constraints]{Constraints on programs}

\rSec3[constraints.overview]{Overview}
Expand Down