Philippe Vaucher

OMG... as surprising as it is, it's slower because it doens't have.... the clang/2.9/include subdirectory that only contains some .h I guess libclang parses some of those and eventually this...

Ok, did some traceing... basically I can see that pretty much a lot of headers from the dir are read and that it results in a PCH being created to...

Hum, I see I forgot about this problem. I think it's safe to say that the original issue (clang_complete's performance) is now addressed with libclang, and for those who insist...

Well try to `locate` it? on my machine it was in `/usr/local/lib/clang/2.9/include`, so try something similar on yours :) Otherwise I could try to upload them somewhere for you to...

So libclang.so has the clang/2.9/include subdirectory with the headers? weird, you'd get more speed than that imho. I could try uploading my version for you to test?

I made a bug report, we'll see how it goes (http://llvm.org/bugs/show_bug.cgi?id=9926).

The PCH section of the help file is useful if you use the clang binary instead of libclang (`g:clang_use_library`).

I already made a bug report a while ago: http://llvm.org/bugs/show_bug.cgi?id=9926 But perhaps it should be improved, feel free to contribute to it.

Well, it'd be nice if you at least said "it happens to me too", because it seems they don't care much about this bug report. Also my data is maybe...

**POLL** Recently Cask broke for images < 24.4 (https://github.com/cask/cask/issues/480). I have 3 options here: 1. Remove Cask for all images. 2. Remove Cask for images < 24.4. 3. Wait until...