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

[valarray] wording needs major overhaul #1071

Closed
AlisdairM opened this issue Nov 18, 2016 · 7 comments
Closed

[valarray] wording needs major overhaul #1071

AlisdairM opened this issue Nov 18, 2016 · 7 comments
Assignees
Labels
big An issue causing a large set of changes, scattered across most of the text.

Comments

@AlisdairM
Copy link
Contributor

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.

@jensmaurer
Copy link
Member

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.

@jensmaurer jensmaurer added lwg Issue must be reviewed by LWG. big An issue causing a large set of changes, scattered across most of the text. labels Nov 18, 2016
@jensmaurer
Copy link
Member

See also #232.

@AlisdairM
Copy link
Contributor Author

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.

@sigfpe
Copy link

sigfpe commented Nov 20, 2016

Whatever we do, I recommend extreme caution. Be careful about edtorial fever overreach.

[removed e-mail quote --jensmaurer]

@AlisdairM
Copy link
Contributor Author

yup - agree that appropriate caution is needed too.

jensmaurer added a commit to jensmaurer/draft that referenced this issue Dec 12, 2016
jensmaurer added a commit to jensmaurer/draft that referenced this issue Dec 13, 2016
jensmaurer added a commit to jensmaurer/draft that referenced this issue Dec 14, 2016
@jensmaurer jensmaurer removed the lwg Issue must be reviewed by LWG. label Dec 18, 2016
jensmaurer added a commit to jensmaurer/draft that referenced this issue Jan 9, 2017
jensmaurer added a commit to jensmaurer/draft that referenced this issue Feb 5, 2017
zygoloid pushed a commit that referenced this issue Feb 6, 2017
@jensmaurer
Copy link
Member

@AlisdairM: After #1215 went in, could you please re-check and name a few examples where we still need improvement, in your opinion?

@AlisdairM
Copy link
Contributor Author

#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.

@jensmaurer jensmaurer self-assigned this Feb 11, 2017
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.
Projects
None yet
Development

No branches or pull requests

3 participants