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
[valarray] wording needs major overhaul #1071
Comments
I can't believe this to be editorial. Rephrasing large bodies of text always risks a subtle semantic change, so this should really be an LWG issue. |
See also #232. |
I think editorially, we can incrementally improve these clauses in various ways without triggering a large paper and asking library to review it - as I believe LWG would rather focus its limited resources elsewhere. Editorially, I think this subclause is far from satisfactory in its current shape, given the improving structure of library clauses over time. Continuous refinement to avoid normative changes though, definitely makes this a 'big' task. |
Whatever we do, I recommend extreme caution. Be careful about edtorial fever overreach. [removed e-mail quote --jensmaurer] |
yup - agree that appropriate caution is needed too. |
Partially addresses cplusplus#1071.
Partially addresses cplusplus#1071.
Partially addresses cplusplus#1071.
Partially addresses cplusplus#1071.
Partially addresses cplusplus#1071.
@AlisdairM: After #1215 went in, could you please re-check and name a few examples where we still need improvement, in your opinion? |
#1215 covers the major concern I had when opening this ticket, and would be happy to close it as resolved, picking up anything else we later find as separate issues. |
This is a large piece of work.
The valarray section does not use the standard section labels,
Requires/Effects/Returns/etc. using free-form text to try to
establish the same guarantees. Other than looking like bad
style, this form of presentation has grown to grant explicit
meaning through these terms, and the valarray specification
would be much clearer if adapted.
The text was updated successfully, but these errors were encountered: