Lines Matching +refs:clang +refs:format
8 When using :program:`clang-format` command line utility or
9 ``clang::format::reformat(...)`` functions from code, one can either use one of
14 Configuring Style with clang-format
17 :program:`clang-format` supports two ways to provide custom style options:
19 use ``-style=file`` and put style configuration in the ``.clang-format`` or
20 ``_clang-format`` file in the project directory.
22 When using ``-style=file``, :program:`clang-format` for each input file will
23 try to find the ``.clang-format`` file located in the closest parent directory
27 The ``.clang-format`` file uses YAML format:
44 When :program:`clang-format` formats a file, it auto-detects the language using
47 used to override the file name :program:`clang-format` uses to detect the
69 # Don't format .proto files.
77 An easy way to get a valid ``.clang-format`` file containing all configuration
82 clang-format -style=llvm -dump-config > .clang-format
85 is applied for all input files. The format of the configuration is:
95 Clang-format understands also special comments that switch formatting in a
96 delimited range. The code between a comment ``// clang-format off`` or
97 ``/* clang-format off */`` up to a comment ``// clang-format on`` or
98 ``/* clang-format on */`` will not be formatted. The comments themselves
104 // clang-format off
106 // clang-format on
113 When using ``clang::format::reformat(...)`` functions, the format is specified
114 by supplying the `clang::format::FormatStyle
115 <https://clang.llvm.org/doxygen/structclang_1_1format_1_1FormatStyle.html>`_
131 This option is supported only in the :program:`clang-format` configuration
132 (both within ``-style='{...}'`` and the ``.clang-format`` file).
158 Not a real style, but allows to use the ``.clang-format`` file from the
1031 In the .clang-format configuration file, this can be configured like:
2022 clang-format will respect the input's line breaking decisions within
2095 If ``true``, format braced lists as best suited for C++11 braced
2105 (e.g. a type or variable name), clang-format formats as if the ``{}`` were
2249 If ``true``, clang-format detects whether function calls and
2254 made, clang-format analyzes whether there are other bin-packed cases in
2261 If ``true``, clang-format adds missing namespace end comments for
2284 In the .clang-format configuration file, this can be configured like:
2363 To configure this in the .clang-format file, use:
2368 - Regex: '^"(llvm|llvm-c|clang|clang-c)/'
2398 By default, clang-format considers files as "main" only when they end
2674 In the .clang-format configuration file, this can be configured like
2757 Language, this format style is targeted at.
2787 Should be used for Protocol Buffer messages in text format
3046 style for that language defined in the .clang-format file. If no style has
3047 been defined in the .clang-format file for the specific language, a
3059 To configure this in the .clang-format file, use:
3079 If ``true``, clang-format will attempt to re-flow comments.
3116 Controls if and how clang-format will sort ``#includes``.
3188 If ``true``, clang-format will sort using declarations.
3539 Parse and format C++ constructs compatible with this standard.
3549 Parse and format as C++03.
3553 Parse and format as C++11.
3556 Parse and format as C++14.
3559 Parse and format as C++17.
3562 Parse and format as C++20.
3565 Parse and format using the latest supported language version.
3596 clang-format aware of such cases.
3613 In the .clang-format configuration file, this can be configured like:
3660 In the .clang-format configuration file, this can be configured like:
3673 Each additional style option adds costs to the clang-format project. Some of
3674 these costs affect the clang-format development itself, as we need to make
3680 The goal of the clang-format project is more on the side of supporting a