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.

Sign up for GitHub

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

Jump to bottom

fix use of "for some" throughout [ranges] #3136

Closed
zygoloid opened this issue Aug 6, 2019 · 1 comment · Fixed by #3146
Closed

fix use of "for some" throughout [ranges] #3136

zygoloid opened this issue Aug 6, 2019 · 1 comment · Fixed by #3146
Assignees
@CaseyCarter

Comments

@zygoloid
Copy link
Member

zygoloid commented Aug 6, 2019

In [ranges] (and possibly elsewhere in range-related wording) we find utterances such as:

Within this clause, for some integer-like type X (23.3.4.4), make-unsigned-like-t(X) denotes make_unsigned_t if X is an integer type;

and

For some subexpressions E and F, the expression view::take_while(E, F) is expression-equivalent to take_while_view{E, F}.

These are uniformly wrong; they mean "for any" or "for given" (∀) not "for some" (∃).
@jensmaurer jensmaurer mentioned this issue Aug 6, 2019
Closed
@CaseyCarter
Copy link
Contributor

CaseyCarter commented Aug 6, 2019 •
edited

We discussed this in LWG Cologne: I was instructed to file an editorial issue to omit the "some" in the "equivalent to foo(E) , for some subexpression E" and "equivalent to bar(E, F), for some subexpressions E and F" cases. (Notably this contradicts the guidance LWG gave me in Batavia and/or San Diego to add the "some"s.)

I'll prepare a PR for this, and address other "for some"s that actually mean "for any" / "for an arbitrary".

CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Aug 6, 2019
@CaseyCarter
Library-wide: don't use "for some" to mean "for an arbitrary"
3d848a1 
Affects: [cmp.alg], [concept.convertibleto], [concept.swappable], [concept.boolean], [concept.equalitycomparable], [concept.stricttotallyordered], [iterator.cust.move], [iterator.cust.swap], and many subclauses of [ranges]

Fixes cplusplus#3136.
@CaseyCarter CaseyCarter mentioned this issue Aug 6, 2019
Merged
CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Oct 1, 2019
@CaseyCarter
Library-wide: don't use "for some" to mean "for an arbitrary"
85baab1 
Affects: [cmp.alg], [concept.convertibleto], [concept.swappable], [concept.boolean], [concept.equalitycomparable], [concept.stricttotallyordered], [iterator.cust.move], [iterator.cust.swap], and many subclauses of [ranges]

Fixes cplusplus#3136.
CaseyCarter added a commit to CaseyCarter/draft that referenced this issue Jan 24, 2020
@CaseyCarter
Library-wide: don't use "for some" to mean "for an arbitrary"
c8a4160 
Affects: [cmp.alg], [concept.convertibleto], [concept.swappable], [concept.boolean], [concept.equalitycomparable], [concept.stricttotallyordered], [iterator.cust.move], [iterator.cust.swap], and many subclauses of [ranges]

Fixes cplusplus#3136.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CaseyCarter CaseyCarter

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Library-wide: don't use "for some" to mean "for an arbitrary" CaseyCarter/draft
2 participants
@zygoloid @CaseyCarter