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
Use "denotes a type" in utilities library clause #2678
Conversation
I've rebased it on |
Rebased and a new commit added to make [refwrap.unwrapref] use "denotes the type" too. |
source/utilities.tex
Outdated
otherwise it is \tcode{T}. | ||
the member typedef \tcode{type} of \tcode{unwrap_reference<T>} | ||
denotes the type \tcode{X\&}, | ||
otherwise \tcode{type} denotes the type \tcode{T}. |
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.
It's very much clear here that T
and X&
are types, and that a "member typedef" must denote a type; do we really need "the type" in the two lines above to remind us? "...the member typedef type
of unwrap_reference<T>
denotes X&
, otherwise type
denotes T
" seems perfectly clear and unambiguous to me.
Ditto 17836-37, 17843-44, 17853-54, 17876, 17893, 17970-71, 17998, 18056, 18063-64.
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.
The decision recorded at #2354 (comment) was to say "denotes the type" but I agree that saying it's a type is redundant in many cases.
Rebased and addressed Casey's comments. |
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.
I like it.
Actually I think #2678 (comment) got lost when I rebased, because that wording moved to Annex D and I didn't reapply it correctly. I'll push another commit and check if anything else got lost. |
I'll also apply the change requested at #2678 (comment) to This was a pain to rebase, because every single change moved from |
Oh, yes, sorry about that -- thanks a lot! |
OK, I think all changes are present and correct. |
I don't think we need to keep the individual commits, I think squash+merge makes more sense. But I can rebase it to remove the FIXUP ones if you want the individual commits. |
Yes, if a smaller number, but still more than one, makes sense, then a bit of grouping and separation is also nice. |
Also use "denotes" instead of "names" for member typedefs.
OK, cleaned up a bit and rebased. I'll leave this for a day or so for other comments and then merge. |
I actually like the individual commits. Very tidy. |
This replaces #2354, in line with the editorial meeting decision.