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

fix presentation of tuple_element specializations #2786

Closed
zygoloid opened this issue Mar 15, 2019 · 2 comments · Fixed by #2868
Closed

fix presentation of tuple_element specializations #2786

zygoloid opened this issue Mar 15, 2019 · 2 comments · Fixed by #2868
Assignees

Comments

@zygoloid
Copy link
Member

We have a variety of tuple_element specializations that use different presentation styles:

  • Some give a definition of the specialization
  • Others don't, and merely specify the ::type member
  • Some use a Value: element for the type, others use a Type: element

We should do this properly: the specialization needs a specified definition, and a member typedef should be specified as actually being a type. (The current wording for several of these specializations completely lacks any suggestion that ...::type is a typedef-name, for example.)

@JohelEGP
Copy link
Contributor

#2553, #2476 and https://wg21.link/LWG3166 are related.

@jensmaurer
Copy link
Member

jensmaurer commented May 3, 2019

LWG 3166 is concerned with the undefined "Value:" element. Let's ignore this issue for now (since it's tracked elsewhere), and let's harmonize all tuple_element specialization as outlined by @zygoloid above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants