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

Confusing wording in CWG2300 regarding definitions and token sequences #3155

Closed
burblebee opened this issue Aug 8, 2019 · 2 comments · Fixed by #3267
Closed

Confusing wording in CWG2300 regarding definitions and token sequences #3155

burblebee opened this issue Aug 8, 2019 · 2 comments · Fixed by #3267
Assignees
@jensmaurer

Comments

@burblebee
Copy link
Contributor

CWG2300 appended wording to the first bullet of [basic.def.odr]p12.1 so it now reads:

Given such an entity named D defined in more than one translation unit, then
- each definition of D shall consist of the same sequence of tokens, for which the definition of a closure type is considered to consist of the sequence of tokens of the corresponding /lambda-expression/; and

What are we saying here? Can this be clarified editorially?
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 10, 2019
@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Sep 30, 2019
@jensmaurer
Copy link
Member

jensmaurer commented Sep 30, 2019 •
edited

Editorial teleconference: replace "for which" -> "where". Consensus. Don't go with Richard's idea (reduces too much of the handwaving).

@zygoloid
Copy link
Member

zygoloid commented Sep 30, 2019 •
edited

Possible alternative to consider:

each definition of D shall be formed from the same sequence of tokens, where

  • a definition produced by a declaration is formed from the sequence of tokens in its declaration, and
  • a definition of a closure type is formed from the sequence of tokens in its lambda-expression; and

@jensmaurer jensmaurer self-assigned this Oct 3, 2019
@jensmaurer jensmaurer mentioned this issue Oct 3, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[basic.def.odr] Replace misleading 'for which' with 'where'. jensmaurer/draft
3 participants
@zygoloid @burblebee @jensmaurer