marvin2k

this issue seems still to be true -- at least in my world. may this could be mentioned more prominently? here is the corresponding snippet from my vimrc: "clang... "...

yes, no problem. compilation: g++ complete.cc -o complete -lclang -L$HOME/llvm.install/lib -I$HOME/llvm.install/include tested on 3 systems, each time first with additional includes (working and fast) and then without (works too, but...

hm, thank for reporting at llvm. I'll keep my mouth shut, this should be enough to point the ones who know to the right direction ;-)

@tobig could you comment on which version of (lib)clang or llvm you are using, and from which source? as mentioned in issue #152 i had severe problems using the current...

sorry, i meant issue #152 ;-) hm I thought during testing for issue #152 that the include-thingy seemed to be fixed because leaving them didn't change anything performance wise... so...

Uh, hadn't realized the incremental aspect. It seems to work, but removing cpp/hpp files might cause problems? Yeah, cleaning the `${srcprjct}` and `${bldprojct}` prior to running sounds like a good...

ui. Gut zu wissen. Wir müssten mal rebasen ;-) On 08/10/2017 12:02 PM, Markus Goetz wrote: > > FYI #58 was > merged which partly overlaps here > > —...

Yaml input would be a nice option as it is more human-readable. But there might also be people objecting because yaml tends to be slower. And both points will cause...