Q_FOREACH and foreach are anachronisms. Range based for may cause a performance regression: it can lead to a copy of shared containers (one reason why Qt's COW containers are broken). However, as long as there is no user noticeable delay, there is no point in analyzing each case. And also no point in slapping an 'asConst' on every container that is looped over. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
24 lines
898 B
YAML
24 lines
898 B
YAML
AccessModifierOffset: -8 # so public: and private: stays at the left site
|
|
AlignEscapedNewlinesLeft: true
|
|
AllowAllParametersOfDeclarationOnNextLine: false
|
|
BinPackParameters: true
|
|
BreakBeforeBinaryOperators: false
|
|
BreakBeforeBraces: Linux
|
|
BreakBeforeTernaryOperators: false
|
|
BreakConstructorInitializersBeforeComma: false
|
|
ColumnLimit: 0
|
|
ConstructorInitializerAllOnOneLineOrOnePerLine: true
|
|
ConstructorInitializerIndentWidth: 8
|
|
ContinuationIndentWidth: 8
|
|
ForEachMacros: [ 'for_each_dc', 'for_each_relevant_dc', 'for_each_dive', 'for_each_line' ]
|
|
IndentFunctionDeclarationAfterType: false #personal taste, good for long methods
|
|
IndentWidth: 8
|
|
MaxEmptyLinesToKeep: 2
|
|
NamespaceIndentation: All
|
|
PointerBindsToType: false
|
|
SpaceBeforeAssignmentOperators: true
|
|
# SpaceBeforeParens doesn't work --> SpaceBeforeParens: ControlStatements
|
|
SpacesBeforeTrailingComments: 1
|
|
SpacesInParentheses: false
|
|
UseTab: Always
|