libclang has nothing to do with clangd so I don't see why having the last one is the reason to remove features from libclang. Especially without reviews.
bkramer arphaman nik
- rGc5929138f58e: [libclang] Revert removal of tidy plugin support from libclang introduced in…
rC348764: [libclang] Revert removal of tidy plugin support from libclang introduced in…
rL348764: [libclang] Revert removal of tidy plugin support from libclang introduced in…
I'd be interested in hearing how this is used. I added this feature as an experiment a while back but it simply didn't work as I envisioned it to. Some checks do work but the overall latency makes it unusable in an IDE setting. People repeatedly asked me to remove it because it slows down builds while not adding value.
We use it with Qt Creator and you can see that we make additions/fixes in libclang from time to time.
With tidy checks selected it is slow indeed but there's always a choice whether to enable checks or not. And if you have very few checks enabled it performs quite fine. And we are still using libclang because we already have infrastructure on top of it which can't be just replaced with clangd (at least it requires quite some time).