Add examples to clang-format configuration

[sylvestre.ledru]

If you think it makes sense, I will do that for the rest of the options

[klimek]

docs/ClangFormatStyleOptions.rst

218

Do we really align these 3 spaces out?

447

Don't we align the : further to the right?

517

I thought we don't do that for single lines?

729

Missing the space?

[sylvestre.ledru]

docs/ClangFormatStyleOptions.rst

218

nope, bad copy and paste it seems. Sorry

447

Yes, sorry, issue during the copy and paste :(

517

Yes and no. I reported this bug:
https://bugs.llvm.org//show_bug.cgi?id=32117
I will update the example to avoid the confusion

[sylvestre.ledru]

With the rst generation

[djasper]

Hm. I don't actually know whether these examples are useful as is. You only present one setting of the value in most cases. What's interesting is actually how the flag changes the behavior. I mean in most cases, this can be derived from the example, but in those cases, it's also fairly obvious what the flag does. Unfortunately, I also don't have a significantly better idea. Maybe something like https://clangformat.com/ is just better at handling this?

include/clang/Format/Format.h

661

"update" seems like the wrong word. Maybe "affected"?

[sylvestre.ledru]

I see a lot of values in examples. If I started this review, it is because I was lost in all the options and could not find what I was looking for.

If you want, I can update the example to provide results with and without the option.

like

With SpacesInCStyleCastParentheses: true:
x = ( int32 )y
With false:
x = (int32)y

[djasper]

Sure, then go ahead. If these examples would have helped you, that's one datapoint :).

As for presenting the difference in options, that would be useful I think. So if you are up to also doing that, that'd be appreciated.
For bool options it seems easiest to do something like:

true:  x = ( int32 )y;
false: x = (int32)y;

(I'd try to keep this as compact as possible for now as the style page getting much longer also hurts discoverability)

[kimgr]

For what it's worth, I also find this useful to be able to see at a glance what the setting does. I know I've tried several different settings in the past before finding the one I was looking for.

[sylvestre.ledru]

For bool options it seems easiest to do something like:
true: x = ( int32 )y;
false: x = (int32)y;

That works for single declarations but for stuff like:

SomeClass::Constructor()
        : a(a)
        , b(b)
        , c(c) {}

I won't be great :/

[djasper]

I agree, just generally we should aim for keeping these short.

The example you gave might actually be reasonable to compare in two columns, i.e.:

true:                                  false:
SomeClass::Constructor()      vs.      SomeClass::Constructor() : a(a),
        : a(a)                                                    b(b),
        , b(b)                                                    c(c) {}
        , c(c) {}

or some such.

[krasimir]

I also think that examples for the flags are good. My use case is that while developing/debugging its nice to see a short example for a random flag in the documentation pop-up.

[sylvestre.ledru]

With the changes requested by Daniel. This is much better indeed!

[sylvestre.ledru]

updated => affected
+ align the vs

[sylvestre.ledru]

Daniel, it is good for me now.
Once it is accepted, I will work on the rest in a separate commit if that is ok with you;

[djasper]

Looks good. Thank you for doing this!

docs/ClangFormatStyleOptions.rst

   If ``true``, aligns escaped newlines as far left as possible.
   Otherwise puts them into the right-most column.
 
+  .. code-block:: c++
+
+    #define A   \
+    int aaaa;   \
+    int b;      \
+    int dddddddddd;
+
 **AlignOperands** (``bool``)
   If ``true``, horizontally align operands of binary and ternary
   expressions.

 **AlignTrailingComments** (``bool``)
   If ``true``, aligns trailing comments.
 
+  .. code-block:: c++
+
+    int a;     // My comment about a
+    int b = 2; // comment about b
+
 **AllowAllParametersOfDeclarationOnNextLine** (``bool``)
   Allow putting all parameters of a function declaration onto
   the next line even if ``BinPackParameters`` is ``false``.

 **AllowShortCaseLabelsOnASingleLine** (``bool``)
   If ``true``, short case labels will be contracted to a single line.
 
+  .. code-block:: c++
+
+    switch (a) {
+       case 1: x = 1; break;
+       case 2: return;
+    }
+
 **AllowShortFunctionsOnASingleLine** (``ShortFunctionStyle``)
   Dependent on the value, ``int f() { return 0; }`` can be put on a
   single line.

   the string at that point leads to it being indented
   ``ContinuationIndentWidth`` spaces from the start of the line.
 
+  .. code-block:: c++
+
+     aaaa =
+         "bbbb"
+         "cccc";
+
 **AlwaysBreakTemplateDeclarations** (``bool``)
   If ``true``, always break after the ``template<...>`` of a template
   declaration.
 
+  .. code-block:: c++
+
+     template <typename T>
+     class C {};
+
 **BinPackArguments** (``bool``)
   If ``false``, a function call's arguments will either be all on the
   same line or will have one line each.

   Always break constructor initializers before commas and align
   the commas with the colon.
 
+  .. code-block:: c++
+
+     SomeClass::Constructor()
+     : a(a)
+     , b(b)
+     , c(c) {}
+
 **BreakStringLiterals** (``bool``)
   Allow breaking string literals when formatting.
 

   If ``true``, clang-format adds missing namespace end comments and
   fixes invalid existing ones.
 
+  .. code-block:: c++
+
+     namespace a {} // namespace a;
+
 **ForEachMacros** (``std::vector<std::string>``)
   A vector of macros that should be interpreted as foreach loops
   instead of as function calls.

 **SpaceAfterTemplateKeyword** (``bool``)
   If ``true``, a space will be inserted after the 'template' keyword.
 
+  .. code-block:: c++
+
+     template<int> void foo();
+
 **SpaceBeforeAssignmentOperators** (``bool``)
   If ``false``, spaces will be removed before assignment operators.
 
+  .. code-block:: c++
+
+     int a = 5;
+     a += 42
+
 **SpaceBeforeParens** (``SpaceBeforeParensOptions``)
   Defines in which cases to put a space before opening parentheses.
 

   If ``true``, spaces will be inserted after ``<`` and before ``>``
   in template argument lists.
 
+  .. code-block:: c++
+
+     static_cast< int >(arg);
+     std::function< void(int, int) > fct;
+
 **SpacesInCStyleCastParentheses** (``bool``)
   If ``true``, spaces may be inserted into C style casts.
 
+  .. code-block:: c++
+
+     x = ( int32 )y
+
 **SpacesInContainerLiterals** (``bool``)
   If ``true``, spaces are inserted inside container literals (e.g.
   ObjC and Javascript array and dict literals).

 **SpacesInParentheses** (``bool``)
   If ``true``, spaces will be inserted after ``(`` and before ``)``.
 
+  .. code-block:: c++
+
+     SomeType MemberFunction( const Deleted & ) & = delete;
+
 **SpacesInSquareBrackets** (``bool``)
   If ``true``, spaces will be inserted after ``[`` and before ``]``.
+  Lambdas or unspecified size array declarations will not be updated.
 
+  .. code-block:: c++
+
+     int a[ 5 ];
+     std::unique_ptr<int[]> foo() {} // Won't be updated
+
 **Standard** (``LanguageStandard``)
   Format compatible with this standard, e.g. use ``A<A<int> >``
   instead of ``A<A<int>>`` for ``LS_Cpp03``.

include/clang/Format/Format.h

 
   /// \brief If ``true``, aligns escaped newlines as far left as possible.
   /// Otherwise puts them into the right-most column.
+  /// \code
+  ///   #define A   \
+  ///     int aaaa; \
+  ///     int b;    \
+  ///     int dddddddddd;
+  /// \endcode
   bool AlignEscapedNewlinesLeft;
 
   /// \brief If ``true``, horizontally align operands of binary and ternary

   bool AlignOperands;
 
   /// \brief If ``true``, aligns trailing comments.
+  /// \code
+  ///   int a;     // My comment about a
+  ///   int b = 2; // comment about b
+  /// \endcode
   bool AlignTrailingComments;
 
   /// \brief Allow putting all parameters of a function declaration onto

   bool AllowShortBlocksOnASingleLine;
 
   /// \brief If ``true``, short case labels will be contracted to a single line.
+  /// \code
+  ///   switch (a) {
+  ///      case 1: x = 1; break;
+  ///      case 2: return;
+  ///   }
+  /// \endcode
   bool AllowShortCaseLabelsOnASingleLine;
 
   /// \brief Different styles for merging short functions containing at most one

   /// in a file look more consistent. Thus, it will only take effect if wrapping
   /// the string at that point leads to it being indented
   /// ``ContinuationIndentWidth`` spaces from the start of the line.
+  /// \code
+  ///    aaaa =
+  ///        "bbbb"
+  ///        "cccc";
+  /// \endcode
   bool AlwaysBreakBeforeMultilineStrings;
 
   /// \brief If ``true``, always break after the ``template<...>`` of a template
   /// declaration.
+  /// \code
+  ///    template <typename T>
+  ///    class C {};
+  /// \endcode
   bool AlwaysBreakTemplateDeclarations;
 
   /// \brief If ``false``, a function call's arguments will either be all on the

 
   /// \brief Always break constructor initializers before commas and align
   /// the commas with the colon.
+  /// \code
+  ///    SomeClass::Constructor()
+  ///        : a(a)
+  ///        , b(b)
+  ///        , c(c) {}
+  /// \endcode
   bool BreakConstructorInitializersBeforeComma;
 
   /// \brief Break after each annotation on a field in Java files.

 
   /// \brief If ``true``, clang-format adds missing namespace end comments and
   /// fixes invalid existing ones.
+  /// \code
+  ///    namespace a {
+  ///    foo();
+  ///    } // namespace a;
+  /// \endcode
   bool FixNamespaceComments;
 
   /// \brief A vector of macros that should be interpreted as foreach loops

   bool SpaceAfterCStyleCast;
 
   /// \brief If \c true, a space will be inserted after the 'template' keyword.
+  /// \code
+  ///    template <int> void foo();
+  /// \endcode
   bool SpaceAfterTemplateKeyword;
 
   /// \brief If ``false``, spaces will be removed before assignment operators.
+  /// \code
+  ///    int a = 5;
+  ///    a += 42
+  /// \endcode
   bool SpaceBeforeAssignmentOperators;
 
   /// \brief Different ways to put a space before opening parentheses.

 
   /// \brief If ``true``, spaces will be inserted after ``<`` and before ``>``
   /// in template argument lists.
+  /// \code
+  ///    static_cast< int >(arg);
+  ///    std::function< void(int, int) > fct;
+  /// \endcode
   bool SpacesInAngles;
 
   /// \brief If ``true``, spaces are inserted inside container literals (e.g.

   bool SpacesInContainerLiterals;
 
   /// \brief If ``true``, spaces may be inserted into C style casts.
+  /// \code
+  ///    x = ( int32 )y
+  /// \endcode
   bool SpacesInCStyleCastParentheses;
 
   /// \brief If ``true``, spaces will be inserted after ``(`` and before ``)``.
+  /// \code
+  ///    SomeType MemberFunction( const Deleted & ) & = delete;
+  /// \endcode
   bool SpacesInParentheses;
 
   /// \brief If ``true``, spaces will be inserted after ``[`` and before ``]``.
+  /// Lambdas or unspecified size array declarations will not be updated.
+  /// \code
+  ///    int a[ 5 ];
+  ///    std::unique_ptr<int[]> foo() {} // Won't be updated
+  /// \endcode
   bool SpacesInSquareBrackets;
 
   /// \brief Supported language standards.