[clang-format] Feature request: ability to break after ( / before ) in control flow statements

[emilyy-dev]

After searching the clang-format style options webpage, I found no option to break after an opening parenthesis or before a closing one in control flow statements (if/for/while/do while), I was hoping to be able to have a format like this

for (
    someReallyLongInit;
    someReallyLongPredicate;
    someReallyLongStep
) {
  // ...
}

if (
    someReallyLongPredicate
) {
  // ...
}

// etc.

The closest setting I could find was AlignAfterOpenBracket with BlockIndent, but that only applies to function invocations, not control flow statements (the documentation does not mention anything about it being specific to function calls, it might be worth noting that).

This formatting setting is available in IntelliJ IDEs (which I have used, hence me hoping I could find it in clang-format!), under File | Settings | Editor | Code Style | [language] | Wrapping and Braces, it has separate settings for for/if/while/do while statements (and for Java also has one for the try-with-resources statement) allowing to "Do not wrap", "Wrap if long", "Chop down if long" and "Wrap always" which control the behaviour of the parentheses and also breaking on the init/cond/iter step in the case of for, or breaking on &&s and ||s in an if/while.

[DoDoENT]

I would also be interested in option that allows this style:

for 
(
    someReallyLongInit;
    someReallyLongPredicate;
    someReallyLongStep
) 
{
    // ...
}

if 
(
    someReallyLongPredicate
) 
{
    // ...
}

// etc.

I haven't seen any options for breaking the line before ( or ), neither for functions nor for control statements. Is such thing feasible to implement?

[gedare]

The closest setting I could find was AlignAfterOpenBracket with BlockIndent, but that only applies to function invocations, not control flow statements (the documentation does not mention anything about it being specific to function calls, it might be worth noting that).

if() statements are supposed to work, and now they should:
#77699

for() loops have not worked.

[gedare]

This behavior is kind of like #62963

It may be possible to add something like that for conditionals. Although that breaking of the function is not based on spilling over the line length.