Earlier during the development of D69764: [clang-format] Add Left/Right Const fixer capability I felt it was no longer necessary to ensure we were not trying to change code which didn't need to change and we felt this could be removed, however I'd like to bring this back for now as I am seeing some false positives in terms of the "replacements"
What I see is the generation of a replacement which is a "No Op" on the original code, I think this comes about because of the merging of replacements:
static const a; -> const static a; -> static const a;
The replacements don't really merge, in such a way as to identify when we have gone back to the original
Also remove the Penalty as I'm not using it (and it became marked as set and no used, I'd rather get rid of it if it means nothing)
I think we need to do this step for now, as many people use the --output-replacements-xml to identify that the file "needs a clang-format"
The same can be seen with the -n or --dry-run option as this uses the replacements to drive the error/warning output.
The message may be confusing, but honestly I don't know what to put in either, since "adding non no op replacements" may be even more confusing.