[PATCH] D90232: [clang-format] Formatting constructor initializer lists by putting them always on different lines (update to D14484)

nhlubek added a comment. I tried to highlight the story with this bug that this commit tries to fix in the following bug report: https://bugs.llvm.org/show_bug.cgi?id=50549 It goes back to 2015 and several people have tried to come up with solutions. The solutions are not complicated but due to

[PATCH] D14484: [clang-format] Formatting constructor initializer lists by putting them always on different lines

nhlubek added a comment. In order to push this forward I have written a bug ticket that highlights this issue: https://bugs.llvm.org/show_bug.cgi?id=50549 The patch is also really simple with the clang-format options that are available nowadays https://github.com/Nikolai-Hlubek/clang/tree/Cons

[PATCH] D14484: [clang-format] Formatting constructor initializer lists by putting them always on different lines

nhlubek added a comment. Required change for break after colon: https://github.com/llvm-mirror/clang/pull/67 New unit test shows use case that is not covered currently. Repository: rL LLVM CHANGES SINCE LAST ACTION https://reviews.llvm.org/D14484/new/ https://reviews.llvm.org/D14484 _

[PATCH] D14484: [clang-format] Formatting constructor initializer lists by putting them always on different lines

nhlubek added a comment. In D14484#1689271 , @MyDeveloperDay wrote: > Looking at this I'm wondering if this Isn't at least partially handled by the > `BreakConstructorInitializersStyle` in combination with > `ConstructorInitializerAllOnOneLineOrOnePerL

[PATCH] D14484: Formatting constructor initializer lists by putting them always on different lines

nhlubek added a comment. Is it possible to discuss about this feature again? This is only a corner case if you allow only 80 characters per line. If you allow more characters (e.g. you use doxygen for inline formatting and want some space on the right) this quickly becomes very relevant, because