On Wed, Jul 6, 2022 at 11:15 AM Daniel P. Berrangé <berra...@redhat.com> wrote: > For clang-tidy, I've been trying it out integrated into emacs > via eglot and clangd. This means I get clang-tidy errors reported > interactively as I write code, so wouldn't need to run a full > tree analysis. Unfortunately, unless I'm missing something, there's > no way to extend clangd to plugin extra checks. So it would need > to re-implement something equivalent to clangd for our custom checks, > and then integrate that into eglot (or equiv for other editors).
That would be very handy. Still, running the script on the whole tree would be necessary to ensure that changes to headers don't break translation units that are not open in the editor. Alberto
