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

Use the Oxford comma in [class.copy.assign]. #2257

Merged
merged 1 commit into from Nov 6, 2018

Conversation

Quuxplusone
Copy link
Contributor

And turn a bunch of \tcode{const} \tcode{X} into \tcode{const X} on the assumption that this is better. (I see the latter style being used elsewhere, and it's certainly more readable in the TeX source.)

\tcode{M}
(or array thereof),
for all the non-static data members of \tcode{X} that are of a class type
\tcode{M} (or array thereof),
Copy link
Member

Choose a reason for hiding this comment

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

Since you're re-flowing the source here: We want semantic linebreaks, but the best position to break seems to be before the "that" (which starts a relative clause).

Copy link
Member

@jensmaurer jensmaurer left a comment

Choose a reason for hiding this comment

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

Please address my comment.

@Quuxplusone
Copy link
Contributor Author

Addressed!

Copy link
Member

@jensmaurer jensmaurer left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@tkoeppe
Copy link
Contributor

tkoeppe commented Sep 12, 2018

Looks good, but could you kindly make and attach diffpdf screenshot (in "appearance" comparison mode)?

@Quuxplusone
Copy link
Contributor Author

could you kindly make and attach diffpdf screenshot

Not I; I haven't got diffpdf. Maybe someone not-me could.

@zygoloid zygoloid added the decision-required A decision of the editorial group (or the Project Editor) is required. label Oct 8, 2018
@zygoloid
Copy link
Member

zygoloid commented Oct 9, 2018

We currently have a mixture of spaces-in-\tcode and spaces-between-\tcodes formatting, and we should pick our preferred options. Example:

With \tcode split on spaces:

image

With spaces inside \tcode:

image

Clearly our full code examples are going to use the spaces-inside-\tcode approach, so perhaps that's better for consistency. But I think splitting \tcode on spaces is more beautiful.

@jensmaurer jensmaurer added the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Oct 9, 2018
@jensmaurer
Copy link
Member

I agree it's more beautiful to split the \tcodes, but it's also less grep-able and less readable in the text editor for the LaTeX source. Let's not split \tcode.

@Quuxplusone
Copy link
Contributor Author

Quuxplusone commented Oct 9, 2018 via email

@jensmaurer
Copy link
Member

@Quuxplusone, could you please rebase, thereby resolving the conflicts?

@jensmaurer jensmaurer removed the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Oct 25, 2018
@jensmaurer
Copy link
Member

Editorial meeting: If the space is part of the technical content (such as the "const volatile X&" example above), the space is part of the \tcode. With that decision made, we merge this change.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 6, 2018
@zygoloid zygoloid merged commit 12935b8 into cplusplus:master Nov 6, 2018
@Quuxplusone Quuxplusone deleted the oxford-comma branch February 5, 2019 19:25
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

4 participants