You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
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.
We have a variety of
tuple_element
specializations that use different presentation styles:::type
memberWe 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.)The text was updated successfully, but these errors were encountered: