[cfe-dev] Dependencies between tools
Chris Gray via cfe-dev
cfe-dev at lists.llvm.org
Thu Apr 19 10:29:53 PDT 2018
Hi Ilya, I actually didn't have much of a plan -- I just wanted to see if I
could do it. I was assuming that there would be a mechanism for starting
asynchronous work that could add to the list of diagnostics, but I hadn't
gotten there yet. I do think that coming up with some sort of way to have
inter-tool dependencies would be nice regardless of whether it's currently
feasible to add clang-tidy diagnostics to clangd. (I guess I'm saying that
both problems will eventually need to be solved, and it makes sense to
concentrate on them separately.)
On Thu, Apr 19, 2018 at 3:05 AM Ilya Biryukov <ibiryukov at google.com> wrote:
> Hi Chris,
> Before getting into low-level details, could you elaborate on design
> you're planning for this?
> We had plans to integrate clang-tidy before, but it's not as simple as
> running clang-tidy before reporting diagnostics.
> Since clang-tidy diagnostics are slow, we want to make sure they don't
> hurt user-experience of other features.
> I.e. go-to-definition, compiler diags and code completion should not be
> blocked or get slower after we add clang-tidy.
> On Thu, Apr 19, 2018 at 9:20 AM Chris Gray via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
>> Hi, I'm looking into integrating clang-tidy's diagnostics into clangd,
>> but I'm running into problems because clang-tidy's headers seem effectively
>> private from clangd's point of view. (I can include
>> "../clang-tidy/ClangTidy.h", but that seems like a pretty bad hack). Is
>> there a way that the libraries in tools/extra can export public headers so
>> that other tools can use them? Or should we be putting the functionality
>> that we want to share in a library in clang proper?
>> cfe-dev mailing list
>> cfe-dev at lists.llvm.org
> Ilya Biryukov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev