| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/google/ |
| H A D | readability-braces-around-statements.rst | 1 .. title:: clang-tidy - google-readability-braces-around-statements
3 :http-equiv=refresh: 5;URL=../readability/braces-around-statements.html
5 google-readability-braces-around-statements
8 The google-readability-braces-around-statements check is an alias, please see
9 `readability-braces-around-statements <../readability/braces-around-statements.html>`_
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/hicpp/ |
| H A D | braces-around-statements.rst | 1 .. title:: clang-tidy - hicpp-braces-around-statements
3 :http-equiv=refresh: 5;URL=../readability/braces-around-statements.html
5 hicpp-braces-around-statements
8 The `hicpp-braces-around-statements` check is an alias, please see
9 `readability-braces-around-statements <../readability/braces-around-statements.html>`_
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/readability/ |
| H A D | braces-around-statements.rst | 1 .. title:: clang-tidy - readability-braces-around-statements
3 readability-braces-around-statements
6 `google-readability-braces-around-statements` redirects here as an alias for
10 ``while``) are inside braces.
37 `0` means that braces will be added to all statements (not having them
|
| H A D | misleading-indentation.rst | 8 Missing braces can also make it significantly harder to read the code,
9 therefore it is important to use braces.
14 You can omit braces when your inner part of e.g. an ``if`` statement has only
29 // Missing braces:
|
| /llvm-project-15.0.7/flang/tools/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements'
|
| /llvm-project-15.0.7/flang/ |
| H A D | .clang-tidy | 1 Checks: '-llvm-include-order,readability-braces-around-statements,-readability-identifier-naming,-c…
|
| /llvm-project-15.0.7/flang/lib/FrontendTool/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/lib/Lower/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/lib/Optimizer/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/lib/Frontend/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/unittests/Frontend/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/include/flang/Lower/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/include/flang/FrontendTool/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/include/flang/Optimizer/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/include/flang/Frontend/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/flang/tools/flang-driver/ |
| H A D | .clang-tidy | 1 Checks: '-readability-braces-around-statements,readability-identifier-naming,llvm-include-order,cla…
|
| /llvm-project-15.0.7/polly/lib/External/isl/doc/ |
| H A D | CodingStyle | 23 - if either the then or the else branch of an if has braces,
24 then they both have braces
|
| /llvm-project-15.0.7/libc/AOR_v20.02/ |
| H A D | config.mk | 18 CFLAGS += -Wall -Wno-missing-braces
|
| H A D | config.mk.dist | 16 CFLAGS += -Wall -Wno-missing-braces
|
| /llvm-project-15.0.7/llvm/utils/lit/tests/Inputs/shtest-if-else/ |
| H A D | test.txt | 19 # Spaces inside curly braces are not ignored
86 # Substitutions with braces are handled correctly
|
| /llvm-project-15.0.7/clang-tools-extra/test/clang-tidy/checkers/cppcoreguidelines/ |
| H A D | init-variables.cpp | 80 int braces{42}; in init_unit_tests() local
|
| /llvm-project-15.0.7/lldb/include/lldb/Core/ |
| H A D | Highlighter.h | 74 ColorStyle braces; member
|
| /llvm-project-15.0.7/clang/test/CodeGenCXX/ |
| H A D | auto-var-init.cpp | 31 type_##NAME braces = {}; \
32 used(braces); \
|
| /llvm-project-15.0.7/lld/test/ELF/linkerscript/ |
| H A D | operators.test | 46 braces = 1 + (2 + 3) * 4;
98 # CHECK-NEXT: 0000000000000015 A braces
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | CodingStandards.rst | 495 formatting braced initialization lists: act as-if the braces were parentheses
643 // The Foo constructor call is reading a file, don't use braces to call it.
646 // The pair is being constructed like an aggregate, use braces.
1588 prefer to omit the braces to avoid unnecessary line noise. However, braces
1630 // Use braces on the outer `if` to avoid a potential dangling `else`
1647 // This should also omit braces. The `for` loop contains only a single
1648 // statement, so it shouldn't have braces. The `if` also only contains a
1654 // Use braces for a `do-while` loop and its enclosing statement.
1661 // Use braces for the outer `if` since the nested `for` is braced.
1678 // Use braces on the outer block because of a nested `if`; otherwise the
[all …]
|