carlosgalvezp wrote: This will be a breaking change for people who post-process the clang-tidy logs in some way and search for `clang-diagnostic-error`:
https://sourcegraph.com/search?q=context:global+clang-diagnostic-error&patternType=keyword&sm=0 I see hits in scripts from "major" organisations like Mozilla, Jenkins, Sonar, Microsoft, etc. I don't however have a feeling for "how much is too much", whether this breakage is acceptable or not. Thus I wonder if we should have a smoother transition like typically do with breaking changes, e.g. a 2-release cycle. I also wonder if this renaming is even worth at all considering the trouble it might give, and if we should instead direct our efforts into documentation instead, to achieve the same goal: provide clarity to our users. https://github.com/llvm/llvm-project/pull/153870 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
