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

Fix some more subscripts for T, also fix cv in a few places. #1805

Merged
merged 2 commits into from Nov 21, 2017

Conversation

jensmaurer
Copy link
Member

No description provided.

of \tcode{reference_wrapper}, then \tcode{Vi} is \tcode{Ui::type\&},
otherwise \tcode{Vi} is \tcode{Ui}.
where \tcode{V1} and \tcode{V2} are determined as follows: Let $\tcode{U}_i$ be
\tcode{decay_t<$\tcode{T}_i$>} for each $\tcode{T}_i$. If $\tcode{U}_i$ is a specialization
Copy link
Contributor

Choose a reason for hiding this comment

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

This is odd now, because it says T1 above on line 938, but here you say T_1.

Copy link
Member Author

Choose a reason for hiding this comment

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

Agreed, it's odd. However, T1, T2, V1, and V2 are actual template parameters, so I can't really use subscript on those. I guess I should drop that particular change and create a new editorial issue with tag "decision required" so that we can talk about it later.

Copy link
Contributor

Choose a reason for hiding this comment

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

Correct, that's why I hadn't made such changes before. If we need the C++ identifier, we should just use that, or otherwise we need to introduce wording like "where T_i is Ti" etc. For abstract type lists, subscripting is good.

@jensmaurer
Copy link
Member Author

Dropped odd change that needs further discussion.

@tkoeppe tkoeppe merged commit ef9e312 into cplusplus:master Nov 21, 2017
@jensmaurer jensmaurer deleted the b10 branch November 21, 2017 23:48
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

Successfully merging this pull request may close these issues.

None yet

2 participants