-
Notifications
You must be signed in to change notification settings - Fork 763
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
base: main
Are you sure you want to change the base?
Conversation
…r [exception.propagation]
ef56ce8
to
6354380
Compare
This comment has been minimized.
This comment has been minimized.
I would like some LWG input on both this PR and the underlying issue. |
It seems to me that some select |
@JohelEGP: If you're unsure if something is editorial, then it's definitely more reliable to start with an LWG issue, and LWG can decide that it's editorial. Otherwise I'll do my best to get LWG's attention, but that process is not terribly reliable. Generally, the less certain I am that something is obviously editorial, the less I'm willing to make changes unilaterally and will try to get some expert input. CWG has a different work load and has been able to review editorial issues from GitHub reguarly recently, but fundamentally the same applies there, too: if something isn't obviously editorial, it's safer to go via the issues lists. We'll do our best here, but just in case you're looking for hard guarantees. |
Thank you. I will consider submitting a LWG issue soon.
I certainly wouldn't like this to go stale. The same might apply to others who have their issues labeled. Do you think that information is fit for the wiki? Or perhaps just being more clear as to how the WG's input should come about: you contacting them (perhaps with no hard guarantees) or the issues' author submitting an issue. |
Maybe? We already say, "If you are not sure whether your proposed edit falls into the above categories, you should consider submitting it as a technical issue instead.", but we could add that we'll try our best to triage and redirect, but without guarantees? |
Well, it's been a long time since I've read that. I suppose it's already clear enough. |
If you do get an LWG issue number, please let us know in a comment. |
@@ -2218,6 +2220,24 @@ | |||
other than \tcode{value_type} are complete types. | |||
\end{itemize} | |||
|
|||
\rSec3[exception.propagation]{Exception propagation requirements} |
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.
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.
This is now https://wg21.link/LWG3640. |
Resolves #4863.