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

[range.range] replace hyphens with dashes #3206

Merged
merged 1 commit into from Sep 3, 2019

Conversation

morinmorin
Copy link
Contributor

No description provided.

@@ -839,7 +839,7 @@
model \tcode{\placeholdernc{forwarding-range}}. \tcode{subrange} provides
non-member rvalue overloads of \tcode{begin} and \tcode{end} with the same
semantics as its member lvalue overloads, and \tcode{subrange}'s iterators
- since they are ``borrowed'' from some other range -
-- since they are ``borrowed'' from some other range --
Copy link
Member

Choose a reason for hiding this comment

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

Is an em-dash (three ---) more appropriate for this? Ah, https://en.wikipedia.org/wiki/Dash says we wouldn't have spaces around it then.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I also prefer spaced em dashes. If em dashes were consistently used in the document, I would have used em dahses.

Ah, https://en.wikipedia.org/wiki/Dash says we wouldn't have spaces around it then.

It's definitely OK to put spaces around em dashes — there are two styles (one with spaces and one without spaces).

Is an em-dash (three ---) more appropriate for this?

I just thought that the em dash just after the end of this sentence becomes interfering on the eye, if we use em dashes. But either works for me.

@jensmaurer jensmaurer merged commit 5c13e48 into cplusplus:master Sep 3, 2019
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