Hi folks,
As you know, a couple of years ago I stepped away from maintenance of CDT's homegrown parser/indexer and have been focusing on clang-based tooling instead.
I am keenly interested in something like this. I have found that CDT's indexer is able to detect bugs that don't show up even in the C/C++ Code Analysis tool (and never in compiler warnings or static analyzers). I don't have much experience building LLVM tools, but I do have quite a bit of experience with systems programming, so I would be more than happy to donate spare cycles where I can.
Since then, and especially in the past year, CDT's indexer hasn't really seen much maintenance (from anyone else either).
However, user bug reports in the indexer component have been continuing to trickle in. These concern not only newer language versions that the indexer does not yet support (like C++17), but also regular (e.g. C++98) code using standard library facilities for which the indexer's behaviour regresses over time as new compiler versions ship with new standard library versions that do use C++17 etc., or new compiler built-ins, in their implementation.
The current state of affairs makes me wonder: should the project make some sort of announcement about the CDT indexer's current lack of maintenance? We could then point users who file such bugs to this announcement, so that they're not sitting around waiting for their bug reports to be addressed when that's unlikely to happen.
Regards,
Nate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
Thanks.
- Tim
