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
[basic.scope.class] Use a regular itemize environment instead of enumeraten #1102
Conversation
Eelis
commented
Nov 23, 2016
@zygoloid: Your favourite language concept -- care to review this? |
Why? |
Oh, I just noticed that all other lists use the styling with "(x.y)" numbers in the margin. If there's a subtle reason for this list to be an anomaly, please close, and in that case my apologies for the noise. :) (In that case, it might be worth documenting that reason in the source code.) |
Why special-case this paragraph? |
That's the point. Currently it's a special case, the change makes it consistent with the rest of the standard. |
I'm generally in favour of having fewer different stylistic elements, and this generally looks like the right direction. Ordered lists are very rare and should only be used when something really needs to be done in order (e.g. translation phases). |
The spammy-looking comments come from replying by email rather than on the website. I've edited them to remove the noise. |
Ah I see, cheers! |
@Eelis: Can you take a look at the other |
I am not sure I follow. The (x.y) style was introduced so that we can tell that bullet y is within paragraph x, when referenced. Why is this in the "right sirection"? |
@sigfpe: There's nothing inherently ordered about the items in question, so a regular list seems like the natural choice here. The "right direction" is to remove stylistic deviations like this. It might be interesting to trace the origin of this section; does anyone have the ARM at hand? |
Hmm, I just noticed that the only difference between "enumeraten" and "enumerate" is that the former uses "1)" while the latter uses "1." for the item number. So perhaps a less controversial path forward is to first replace all two "enumeraten" occurrences with "enumerate" (a minimal stylistic change). Then, we can separately decide which "enumerate" occurrences should become "itemize" (a somewhat semantic change). |
If there is nothing inherently ordered, why would an enumeration be the "right direction" then?
Chapter 3 of the ARM didn't bother with this; but I am not sure we need to go back that far.
|
@sigfpe: I don't understand - nobody is proposing an enumeration. We're proposing removing an enumeration and replacing it with an itemization. |
@Eelis: yes, perhaps that'd be a start. Enumerations are so rare that we should probably not need to have more than one stylistic component for them. |
Replying to my own comment earlier regarding ARM: the C++98 version had the current form instead of unnumbered itemized list.
|
Now that #1105 was merged, we can start to consider more generally which enumerations should be replaced with itemizations, but this pull request is not the best place for that. Closing. |
@Eelis: We could still try to get rid of |