This project seems to be very similar to clangd. It is also similar to YouCompleteMe, though YCM does not support LSP yet. How does Cquery compare to those projects in terms of features?

In particular, should it be considered as an alternative to clangd? Could it make sense to combine efforts between clangd and Cquery?

At the moment, clangd and ycm are very similar projects; they are very limited compared to cquery. clangd and ycm support code completion, diagnostics, fixits, and goto declaration (but not definition), whereas cquery supports references, derived types, callers, etc. Basically, if the feature requires knowledge across multiple translation units, clangd/ycm do not support it.

cquery is designed to support very large projects, so it makes very specific design decisions w.r.t. the data model, indexing pipeline, and multithreading model. I hope clangd can match the performance - but so far every project I've seen simply does not run nearly fast enough on a code-base the size of Chrome/ChromeOS.

Thanks for the explanations!

In the meantime I tried it out with VSCode on my MacBook. Works like a charm! Awesome job!!!

Nice to see Swift added to the list of targets. Any idea about the performance of generated parsers in Swift vs other targets?

Somewhat related discussion about a possibility of building tracing JITs for other languages on top of the LuaJIT code base:

http://www.freelists.org/post/luajit/To-which-extent-LuaJIT-...