-
Notifications
You must be signed in to change notification settings - Fork 30
/
.clang-format
63 lines (56 loc) · 2.85 KB
/
.clang-format
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
BasedOnStyle: Google
# If true, if (a) return; can be put on a single line.
AllowShortIfStatementsOnASingleLine: false
# If true, while (true) continue; can be put on a single line.
AllowShortLoopsOnASingleLine: false
# Dependent on the value, int f() { return 0; } can be put on a single line.
AllowShortFunctionsOnASingleLine: true
# The column limit.
# A column limit of 0 means that there is no column limit. In this case, clang-format will respect the input’s line breaking decisions within statements.
ColumnLimit: 80
# If true, format braced lists as best suited for C++11 braced lists.
Cpp11BracedListStyle: true
# Format compatible with this standard, e.g. use A<A<int> > instead of A<A<int>> for LS_Cpp03.
# Possible values:
# LS_Cpp03 (in configuration: Cpp03) Use C++03-compatible syntax.
# LS_Cpp11 (in configuration: Cpp11) Use features of C++11 (e.g. A<A<int>> instead of A<A<int> >).
# LS_Auto (in configuration: Auto) Automatic detection based on the input.
Standard: Cpp11
# Regular expressions denoting the different #include categories used for ordering #includes.
# - POSIX extended regular expressions are supported.
# - These regular expressions are matched against the filename of an include (including the <> or "") in order.
# - The value belonging to the first matching regular expression is assigned and #includes are sorted
# first according to increasing category number and then alphabetically within each category.
# - If none of the regular expressions match, INT_MAX is assigned as category.
# - The main header for a source file automatically gets category 0 so that it is generally kept at
# the beginning of the #includes (https://llvm.org/docs/CodingStandards.html#include-style).
# However, you can also assign negative priorities if you have certain headers that always need to be first.
#
# NOTE: Include here all regex to fulfill Google style guide -> https://google.github.io/styleguide/cppguide.html#Names_and_Order_of_Includes
IncludeCategories:
- Regex: '^(<|")vir/test\.h(>|")' # This has always to be included first => Negative priority
Priority: -1
CaseSensitive: true
- Regex: '^<(sys/)?[^/]*\.h>'
Priority: 1
SortPriority: 0
CaseSensitive: false
- Regex: '^<[[:alnum:]._]+>'
Priority: 2
SortPriority: 0
CaseSensitive: false
- Regex: '^(<|"(Eigen|gsl|HepMC3|Pythia8|Rivet|vir|yaml-cpp)/)[^/]*'
Priority: 3
SortPriority: 0
CaseSensitive: false
- Regex: '^"einhard\.hpp"'
Priority: 3
SortPriority: 0
CaseSensitive: false
- Regex: '^(<|")smash/.*\.h(>|")' # SMASH include should be left in the last block
Priority: 4
CaseSensitive: false
- Regex: '.*'
Priority: 4
SortPriority: 0
CaseSensitive: false