You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several details of code formatting are inconsistent at the moment.
The first step should be to document the desired style on the wiki; then we can clean up the main text by applying the documented style.
Here are some items I noticed repeatedly:
template <class T, class U = T> struct Foo<T, U>
space between template <
no space in template specializations, Foo<T, U>
space around = in U = T
f(a, b , c)
space after comma, not before
no space before the leading parenthesis in function call expressions
Generally, spaces around binary operators except for comma.
Space before leading parenthesis in control structures (for, while, if).
No spaces between closing template brackets: Foo<Bar<T>>. I think there's a separate issue open for this already, but it should go into the style guide in any case.
I think many of those rules are fairly easy to check globally with grep, and so the cleanup shouldn't be terribly difficult or protracted.
The text was updated successfully, but these errors were encountered:
Several details of code formatting are inconsistent at the moment.
The first step should be to document the desired style on the wiki; then we can clean up the main text by applying the documented style.
Here are some items I noticed repeatedly:
template <class T, class U = T> struct Foo<T, U>
template <
Foo<T, U>
=
inU = T
for
,while
,if
).Foo<Bar<T>>
. I think there's a separate issue open for this already, but it should go into the style guide in any case.I think many of those rules are fairly easy to check globally with
grep
, and so the cleanup shouldn't be terribly difficult or protracted.The text was updated successfully, but these errors were encountered: