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

Unify the wording style of saying "T in Types" #974

Closed
lichray opened this issue Nov 9, 2016 · 3 comments
Closed

Unify the wording style of saying "T in Types" #974

lichray opened this issue Nov 9, 2016 · 3 comments
Assignees

Comments

@lichray
Copy link
Contributor

lichray commented Nov 9, 2016

In some places we say "T in Types", some places say "T in Types...", and sometimes followed by a 4th dot (period). We should switch all of these to use the first form.

@W-E-Brown
Copy link
Contributor

On Nov 9, 2016, at 9:36 AM, Zhihao Yuan notifications@github.com wrote:

In some places we say "T in Types", some places say "T in Types...", and sometimes followed by a 4th dot (period). We should switch all of these to use the first form.

While I don't at all mind a unified presentation style, this specific resolution would be not my first choice.

Instead, I recommend "for all T_i constituting Ts" (or, in some cases, "for each of the T_i constituting Ts").

If/when LWG discusses my pending common_type paper, I will lobby for such wording in at least that context. (The published draft uses the word "comprise", but in this specific context, that's the wrong word. If we want to invert the sentence ["Ts is comprised of"], we can keep "comprise", but that seems not universally applicable.)

-- WEB

@lichray
Copy link
Contributor Author

lichray commented Nov 9, 2016

On Nov 9, 2016 11:30 AM, "W-E-Brown" notifications@github.com wrote:

Instead, I recommend "for all T_i constituting Ts" (or, in some cases,
"for each of the T_i constituting Ts").

I'm happy with this suggestion.

Zhihao

tkoeppe added a commit that referenced this issue Feb 5, 2017
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 28, 2017
@jensmaurer
Copy link
Member

jensmaurer commented Jun 7, 2018

Editorial meeting consensus: [tuple.elem] p3+4 is fine as-is, add "If a type T". p5 drop ellipsis after Types. Generally, we want to say "a type T in Types" if we want to talk about an element of the pack "Types". [tuple.special] avoid "Ti", say "for every type T in Types".

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Jun 7, 2018
@jensmaurer jensmaurer self-assigned this Dec 1, 2018
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

No branches or pull requests

3 participants