the_next

Results 19 comments of the_next

入口在 https://github.com/MaskRay/ccls/blob/c6686be382da46baed4245c7963f07964575e90c/src/messages/textDocument_formatting.cc#L70 具体的版本和你编译ccls的时候使用的llvm版本一致,使用的是clang-format提供的sdk

Option 2 looks great, but it may better if LS is more square

for issue https://github.com/MaskRay/ccls/issues/534

> Would be nice to run the tests too. test-index in ccls seem to need clang-6 but I can`t work out with mac, can you help with that?

> Please also correct commit message from "add github ci integrated" to something more verbose like: > > ``` > Add github CI integration. > > CI will be responsible...

I found it happend when the first arg in compile_commmans.json is not clang++ In mac the first arg is /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++, if we replace with /usr/local/opt/llvm/bin/clang++, the `-I../` arg will work

> Please!!, I'm getting errors all the time for not found modules as far as I konw, clang not implement modules yet if the code can be compile by clang,...

as far as i know, the bottleneck of ccls is the cache load speed and compile speed, use sqlite to save cache file may get huge improvement in hdd or...

> > cache load speed > > Is the cache load speed related to the parsing of the `compile_commands.json` file? no i mean the speed to load .ccls-cache direction. now...

![image](https://user-images.githubusercontent.com/26270464/109654617-591bad00-7b9d-11eb-8fa6-e6c28d12ad80.png) 检查一下index都完成了吗,有显示编译错误吗