-
Notifications
You must be signed in to change notification settings - Fork 774
[except.terminate] Better describe the function terminate
#7281
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think "the C++ runtime" is defined. Maybe just "the program"?
Or "Some errors in a program cannot be recovered from, ..." so that we don't talk about "encountering an error", which sounds like it might just be bad luck rather than well-defined control flow that results from the program logic.
94a4ad6
to
425315f
Compare
Much better! Thanks! Applied your suggestion, followed by minor grammar tweaks, and force-pushed to allow a clean merge. |
425315f
to
8277d9d
Compare
terminate
While 'std:terminate' was originally conceived as the way to report failures in the exception handling machinery, it has evolved to become a more general tool for reporting unrecoverable failures in the C++ runtime. This rewording attempts to address that evolving design, and in doing so addresses the outstanding %FIXME% that the current text is not adequately descriptive in the first place.
8277d9d
to
53c6318
Compare
How do we feel about the proposed description now? |
Rebased and force-pushed for good measure. I believe all feedback is addressed, but do we want to flag this for an LWG review as well? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think LWG needs to see this, it seems fairly simple and uncontroversial.
While
std:terminate
was originally conceived as the way to report failures in the exception handling machinery, it has evolved to become a more general tool for reporting unrecoverable failures in the C++ runtime. This rewording attempts to address that evolving design, and in doing so addresses the outstanding %FIXME% that the current text is not adequately descriptive in the first place.