Jim Meyering wrote: > It feels like a good thing to do, but will come with some cost: I have > the impression that relatively few GNU projects use clang (and esp > clang 18), so this testing is likely to expose more "issues". However, > a more diverse set of compilers/warnings may expose real problems in > our code sooner.
I'm not going to hunt down the warnings, only report the errors from the CI. Yes, the idea is to expose the problems sooner. There is no reason why a code change made in June 2024, that is reported by clang from March 2024 as an error in every 'testdir-all' build, needs to propagate into Emacs until it gets noticed. Bruno
