sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-26 04:22:55 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
38b1643fe6
dash/src/.clang-format

62 lines
1.8 KiB
Plaintext
Raw Normal View History

[trivial] clang-format: Set AlignAfterOpenBracket: false
2015-11-02 22:23:52 +01:00
Language: Cpp
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
AccessModifierOffset: -4
Merge #19095: [tools] Update clang-format config for multi-line function declarations and calls cc29d1e2c46e01c544ef44c79d72b7bcc5d39ba7 [tools] Update clang-format config (John Newbery) Pull request description: In some cases, running clang-format has made code _less_ readable by joining declarations and calls for functions with many arguments into very long lines. For example: ``` - size_t getQueueInfo(std::chrono::system_clock::time_point &first, - std::chrono::system_clock::time_point &last) const; + size_t getQueueInfo(std::chrono::system_clock::time_point& first, std::chrono::system_clock::time_point& last) const; ``` (https://github.com/bitcoin/bitcoin/pull/19090#discussion_r431961148) This change to clang-format would allow arguments/parameters for func declarations/calls to be split over multiple lines, aligned with the opening parens. It does not force args/params to be on new lines (that setting is `BinPackParameters : true`). ACKs for top commit: MarcoFalke: ACK cc29d1e2c46e01c544ef44c79d72b7bcc5d39ba7 fine with me practicalswift: ACK cc29d1e2c46e01c544ef44c79d72b7bcc5d39ba7 Tree-SHA512: a62474925e71aaff41bdce7960fd5ffd64317da810f694d8084080b054708cf71c2ab2ce3111db5a9260d1c1f9e02d59a2ecb5543b1b6172ce085cb42432160a
2020-06-21 11:57:48 +02:00
AlignAfterOpenBracket: true
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
AlignEscapedNewlinesLeft: true
AlignTrailingComments: true
fix: apply changes for .clang-format to make it matched with our code style Co-Authored-By: UdjinM6 <UdjinM6@users.noreply.github.com> Co-Authored-By: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
2024-03-21 21:24:18 +01:00
AllowAllArgumentsOnNextLine: false
AllowAllParametersOfDeclarationOnNextLine: false
AllowShortBlocksOnASingleLine: Empty
AllowShortCaseLabelsOnASingleLine: false
AllowShortEnumsOnASingleLine: false
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
AllowShortFunctionsOnASingleLine: All
fix: apply changes for .clang-format to make it matched with our code style Co-Authored-By: UdjinM6 <UdjinM6@users.noreply.github.com> Co-Authored-By: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
2024-03-21 21:24:18 +01:00
AllowShortIfStatementsOnASingleLine: WithoutElse
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
AllowShortLoopsOnASingleLine: false
AlwaysBreakBeforeMultilineStrings: false
AlwaysBreakTemplateDeclarations: true
Update .clang-format to more accurately show the actual style (#2299) * updated clang formatting * add `BreakConstructorInitializers: AfterColon` * revert column limit change * AlignConsecutiveAssignments: true * Revert "AlignConsecutiveAssignments: true" This reverts commit fc4a4a54f7b0d9e725179a3ee1bf0808c08b0da6.
2018-09-20 14:40:00 +02:00
BinPackArguments: true
Merge #21221: [tools] Allow argument/parameter bin packing in clang-format 876ac3f6b62087fb5c22b0a477751895915d47b8 [tools] Allow argument/parameter bin packing in clang-format (John Newbery) Pull request description: clang-format documentation for BinPackArguments: If `false`, a function call’s arguments will either be all on the same line or will have one line each. ``` true: void f() { f(aaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa); } false: void f() { f(aaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa); } ``` https://clang.llvm.org/docs/ClangFormatStyleOptions.html#configurable-format-style-options There's no reason to forbid this format. Having multiple arguments or parameters per line can be just as readable as having one per line (and is certainly more readable than having extremely long lines). ACKs for top commit: laanwj: ACK 876ac3f6b62087fb5c22b0a477751895915d47b8 MarcoFalke: review ACK 876ac3f6b62087fb5c22b0a477751895915d47b8 vasild: ACK 876ac3f6b62087fb5c22b0a477751895915d47b8 Tree-SHA512: 7c401b4551b458c83dd70883860788b4a60e08a5399171fef27a2f5fdc6b933f6454fe0d396c32d826e3ab537791329da3275ae9b5e9ad36630a6dc2c167e88f
2021-02-19 11:28:36 +01:00
BinPackParameters: true
fix: apply changes for .clang-format to make it matched with our code style Co-Authored-By: UdjinM6 <UdjinM6@users.noreply.github.com> Co-Authored-By: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
2024-03-21 21:24:18 +01:00
BreakBeforeBinaryOperators: None
Merge #12982: Fix inconsistent namespace formatting guidelines cd0e1e91dd Fix inconsistent namespace formatting guidelines (Russell Yanofsky) Pull request description: Suggested formatting for namespaces in the developer guide is currently inconsistent. This commit updates the developer guide and clang-format configuration to consistently put "namespace" and opening/closing braces on the same line. Example: ```c++ namespace boost { namespace signals2 { class connection; } // namespace signals2 } // namespace boost ``` Currently the [Source code organization](https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#source-code-organization) section has an example like the one above, but the [Coding style](https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#coding-style) section example and description put a newline between the opening "namespace foo" and brace (but oddly no newline between closing namespace and brace). Avoiding newlines before namespace opening braces makes nested declarations less verbose and also avoids asymmetry with closing braces. It's also a common style used in our own and other codebases: * https://google.github.io/styleguide/cppguide.html#Namespaces * https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes * https://llvm.org/docs/CodingStandards.html#namespace-indentation Tree-SHA512: 507259478e1a7f6f96db386dd04eb25aa04294f533503fdd82368cf809c3ceaa20204b2cb6ae65322eb27446e5934c1aa1ccb6240ead12aa06b314af76f68139
2018-04-17 19:22:13 +02:00
BreakBeforeBraces: Custom
BraceWrapping:
AfterClass: true
AfterFunction: true
Update .clang-format to more accurately show the actual style (#2299) * updated clang formatting * add `BreakConstructorInitializers: AfterColon` * revert column limit change * AlignConsecutiveAssignments: true * Revert "AlignConsecutiveAssignments: true" This reverts commit fc4a4a54f7b0d9e725179a3ee1bf0808c08b0da6.
2018-09-20 14:40:00 +02:00
BreakBeforeTernaryOperators: true
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
BreakConstructorInitializersBeforeComma: false
Update .clang-format to more accurately show the actual style (#2299) * updated clang formatting * add `BreakConstructorInitializers: AfterColon` * revert column limit change * AlignConsecutiveAssignments: true * Revert "AlignConsecutiveAssignments: true" This reverts commit fc4a4a54f7b0d9e725179a3ee1bf0808c08b0da6.
2018-09-20 14:40:00 +02:00
BreakConstructorInitializers: AfterColon
fix: apply changes for .clang-format to make it matched with our code style Co-Authored-By: UdjinM6 <UdjinM6@users.noreply.github.com> Co-Authored-By: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
2024-03-21 21:24:18 +01:00
ColumnLimit: 120
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
CommentPragmas: '^ IWYU pragma:'
ConstructorInitializerIndentWidth: 4
ContinuationIndentWidth: 4
Cpp11BracedListStyle: true
DerivePointerAlignment: false
DisableFormat: false
fix: apply changes for .clang-format to make it matched with our code style Co-Authored-By: UdjinM6 <UdjinM6@users.noreply.github.com> Co-Authored-By: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
2024-03-21 21:24:18 +01:00
FixNamespaceComments: true
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
IndentCaseLabels: false
IndentFunctionDeclarationAfterType: false
IndentWidth: 4
KeepEmptyLinesAtTheStartOfBlocks: false
MaxEmptyLinesToKeep: 2
NamespaceIndentation: None
ObjCSpaceAfterProperty: false
ObjCSpaceBeforeProtocolList: false
fix: apply changes for .clang-format to make it matched with our code style Co-Authored-By: UdjinM6 <UdjinM6@users.noreply.github.com> Co-Authored-By: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
2024-03-21 21:24:18 +01:00
PackConstructorInitializers: Never
PenaltyBreakBeforeFirstCallParameter: 100
PenaltyBreakAssignment: 100
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
PenaltyBreakComment: 300
PenaltyBreakFirstLessLess: 120
Update .clang-format to more accurately show the actual style (#2299) * updated clang formatting * add `BreakConstructorInitializers: AfterColon` * revert column limit change * AlignConsecutiveAssignments: true * Revert "AlignConsecutiveAssignments: true" This reverts commit fc4a4a54f7b0d9e725179a3ee1bf0808c08b0da6.
2018-09-20 14:40:00 +02:00
PenaltyBreakString: 100
PenaltyExcessCharacter: 5
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
PenaltyReturnTypeOnItsOwnLine: 200
PointerAlignment: Left
SpaceBeforeAssignmentOperators: true
SpaceBeforeParens: ControlStatements
SpaceInEmptyParentheses: false
SpacesBeforeTrailingComments: 1
SpacesInAngles: false
SpacesInContainerLiterals: true
SpacesInCStyleCastParentheses: false
SpacesInParentheses: false
fix: apply changes for .clang-format to make it matched with our code style Co-Authored-By: UdjinM6 <UdjinM6@users.noreply.github.com> Co-Authored-By: PastaPastaPasta <6443210+PastaPastaPasta@users.noreply.github.com>
2024-03-21 21:24:18 +01:00
Standard: c++20
Update coding style and add .clang-format
2014-07-09 18:17:23 +02:00
TabWidth: 8
UseTab: Never
Reference in New Issue Copy Permalink