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

Remove "shall equal"s naming from conditional/decay/enable_if #2354

Closed
wants to merge 2 commits into from
Closed

Remove "shall equal"s naming from conditional/decay/enable_if #2354

wants to merge 2 commits into from

Conversation

mclow
Copy link
Contributor

@mclow mclow commented Oct 12, 2018

Instead of saying "shall equal", which implies a condition on the user, we should say "names" or "is".

This change uses 'names', since that's what identity uses: The member typedef type names the type T.
Suggestion from Alisdair.

Instead of saying "shall equal", which implies a condition on the user, we should say "names" or "is".

This change uses 'names', since that's what `identity` uses: The member typedef `type` names the type `T`.
Suggestion from Alisdair.
@@ -16940,15 +16940,15 @@
\tcode{template<bool B, class T = void>} \tcode{struct enable_if;}
&
If \tcode{B} is \tcode{true}, the member typedef \tcode{type}
shall equal \tcode{T}; otherwise, there shall be no member
names \tcode{T}; otherwise, there shall be no member
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/shall be/is/ since you're touching this line anyway?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me. But then, should we fix common_type (probably not, since users can specialize it), basic_common_reference (ditto), invoke_result (probably should).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we should fix those, but notably none of them are on this line. ;)

@jensmaurer
Copy link
Member

I agree with the desire to remove "shall equal", but I'm wondering whether "names the type..." would be better. Otherwise, we have a type-id without any introducer at all.

@W-E-Brown
Copy link
Contributor

W-E-Brown commented Oct 13, 2018 via email

@lichray
Copy link
Contributor

lichray commented Nov 7, 2018

Oh, the issue I wanted to open is already here.

@zygoloid zygoloid changed the title Remove "shall equals" naming from conditional/decay/enable_if Remove "shall equal"s naming from conditional/decay/enable_if Nov 26, 2018
@zygoloid zygoloid added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 26, 2018
@jensmaurer
Copy link
Member

jensmaurer commented Feb 22, 2019

Editorial meeting consensus:

  • Uses "denotes the type".

@jensmaurer jensmaurer added changes requested Changes to the wording or approach have been requested and not yet applied. and removed decision-required A decision of the editorial group (or the Project Editor) is required. labels Feb 22, 2019
@jwakely
Copy link
Member

jwakely commented Feb 22, 2019

#2678 supersedes this PR, so I'm closing this one.

@jwakely jwakely closed this Feb 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes requested Changes to the wording or approach have been requested and not yet applied.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants