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

[containers] "throws an exception" #3207

Open
FrankHB opened this issue Sep 2, 2019 · 7 comments
Open

[containers] "throws an exception" #3207

FrankHB opened this issue Sep 2, 2019 · 7 comments
Labels
big An issue causing a large set of changes, scattered across most of the text. lwg Issue must be reviewed by LWG.

Comments

@FrankHB
Copy link
Contributor

FrankHB commented Sep 2, 2019

Should subclauses in [containers] follow the resolution of LWG 1004?

Further, when do we really need "throws an exception" (if any)?

@FrankHB FrankHB changed the title [container] "throws an exception" [containers] "throws an exception" Sep 2, 2019
@jensmaurer
Copy link
Member

@zygoloid, is this editorial given LWG 1004?

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 2, 2019
@jwakely
Copy link
Member

jwakely commented Sep 2, 2019

It might be better to just add blanket wording to say that when we say a library function throws an exception we are talking about some part of the function throwing or propagating one, and the function not swallowing it.

@jensmaurer
Copy link
Member

@jwakely, why? If we agree that we mean "exits via an exception", we should use these words throughout instead of using other words that might say something we don't mean.

@jwakely
Copy link
Member

jwakely commented Sep 2, 2019

OK, it's just more work to do that, and personally I don't see a large benefit. But some other people in LWG do get upset by the inaccuracy of the current wording.

@jensmaurer
Copy link
Member

Editorial teleconference: Go with "exits via an exception" wherever we say "throws an exception" and we mean the former.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 9, 2019
@jensmaurer
Copy link
Member

jensmaurer commented Sep 10, 2019

It's not obvious how to concisely phrase "Throws: Any exception thrown by <blah>."

(Branch c25.)

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 10, 2019
@jensmaurer jensmaurer added lwg Issue must be reviewed by LWG. and removed decision-required A decision of the editorial group (or the Project Editor) is required. labels Sep 30, 2019
@jensmaurer
Copy link
Member

Editorial teleconference: Just fix the simple cases and punt the rest to LWG.

@jensmaurer jensmaurer added the big An issue causing a large set of changes, scattered across most of the text. label Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
big An issue causing a large set of changes, scattered across most of the text. lwg Issue must be reviewed by LWG.
Projects
None yet
Development

No branches or pull requests

3 participants