On Sun, 2018-03-18 at 18:16 +0100, Miguel Ojeda wrote: > * Uses clang's tooling support behind the scenes to parse and rewrite > the code. It is not based on ad-hoc regexps.
Did you look at the results of a typical and generally style conforming subsystem when reformatted with the new rules you propose here with clang-format? One of the issues with hard-n-fast code formatters like clang-format is taste. clang-format doesn't have any so it can't know when _not_ to reformat blocks according to its rules. Tools like clang-format are generally fine for a first-pass reformat of non-style compliant code, but are IMO generally unsuitable for continuous automated use.
