mirror of
https://github.com/MaskRay/ccls.git
synced 2024-11-22 07:35:08 +00:00
C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
c68548a2ca
% time clang++ -fsyntax-only -std=c++11 a.cc <iostream> => 0.35s <regex> => 0.68s |
||
---|---|---|
ci | ||
src | ||
third_party | ||
.appveyor.yml | ||
.clang_complete | ||
.clang-format | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.pep8 | ||
.travis.yml | ||
.ycm_extra_conf.py | ||
compile_commands.json | ||
README.md | ||
wscript |
cquery
cquery is a highly-scalable, low-latency language server for C/C++/Objective-C. It is tested and designed for large code bases like Chromium. cquery provides accurate and fast semantic analysis without interrupting workflow.
cquery implements almost the entire language server protocol and provides some extra features to boot:
- code completion (with both signature help and snippets)
- finding definition/references
- type hierarchy (parent type, derived types, expandable tree view)
- finding base/derived methods/classes, call tree
- symbol rename
- document and global symbol search
- hover tooltips showing symbol type
- diagnostics
- code actions (clang FixIts)
- darken/fade code disabled by preprocessor
- #include auto-complete, undefined type include insertion, include quick-jump (goto definition, document links)
- auto-implement functions without a definition
- semantic highlighting, including support for rainbow semantic highlighting
>>> Getting started (CLICK HERE) <<<
Limitations
cquery is able to respond to queries quickly because it caches a huge amount of information. When a request comes in, cquery just looks it up in the cache without running many computations. As a result, there's a large memory overhead. For example, a full index of Chrome will take about 10gb of memory. If you exclude v8, webkit, and third_party, it goes down to about 6.5gb.
License
MIT