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
Conversation
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.
source/utilities.tex
Outdated
@@ -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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
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. ;)
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. |
On Oct 13, 2018, at 1:13 PM, Jens Maurer ***@***.***> wrote:
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.
Alternatively, we could rephrase as "denotes" or "denotes the type", as we say in a number of places.
There's also "alias" (as in "is an alias for" or, as a verb, "aliases"). We do already use similar phrasing, e.g., "provides an alias" and "be an alias for".
|
Oh, the issue I wanted to open is already here. |
Editorial meeting consensus:
|
#2678 supersedes this PR, so I'm closing this one. |
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 typedeftype
names the typeT
.Suggestion from Alisdair.