-
Notifications
You must be signed in to change notification settings - Fork 771
Class templates in Clause 33 are not indented #1516
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
Comments
Instead of indenting the entire class bodies by an additional two spaces we could take the approach used by
|
@jwakely: I'm not sure. That doesn't generallze well, and we can't do that for every class template. So perhaps we shouldn't do it for any. There's no problem with indenting that body by another two spaces. |
Uh, it's nowhere indented, it seems: [ios.overview], [vector.overview]. Do you have an example of your desired indentation? |
@jensmaurer: I thought we had already come to a decision on this in a different issue somewhere; check the wiki? [re.traits] would be an example of the style I believe I was referring to, although I think we ultimately decided against that and in favour of the style given in the OP here (in case where we do break the line). |
For example:
This applies to all the lock types,
promise
,future
andpackaged_task
. I'll fix it after motions-2017-03-lwg-17 is merged in, because that adds a new lock type (which is not indented, for local consistency).The text was updated successfully, but these errors were encountered: