On Fri, 28 Jan 2022, Tom Rix wrote: > A testsuite for the fixers may help with churn > > Any interest or thought on organization ? > Here's one way: 1. Identify some source files that are exemplary (i.e. good style). 2. Run a new script to introduce style mistakes into those files. 3. Run the Reformatter Under Test on those files. 4. Compare the output with the original files. But that's not sufficient to prevent more style patches (churn). We still need a way to avoid wasting everyone's time writing, submitting, reviewing and merging the inevitably incomplete style patches that may contain regressions and cause conflicts. The tooling I would like to see is not a script to introduce style mistakes but an editor for binaries, such that C is not the "source" at all but only an ephemeral representation to make it easier for humans to effect changes to binaries (and debug info, commentary etc.) Nonetheless, perfecting the clang-format tool is a good step towards a better workflow, which I described once before. https://lore.kernel.org/r/alpine.LNX.2.23.453.2010281344120.31@nippy.intranet/
