Nathan Ridge

> > If a.c and b.c are linked together, then the foo symbols in the two files are, in fact, the same symbol > > I'm not talking about one...

Indeed, opening a file containing an `#include_next` directive is not well supported. The reason for this is that evaluating an `#include_next` directive requires a piece of state ("which entry in...

> Also, an interesting information is a modifier to indicate if a parameter is passed by non const reference, which would allow the user to see where a variable can...

> Also, an interesting information is a modifier to indicate if a parameter is passed by non const reference, which would allow the user to see where a variable can...

You can control the number of threads used for background indexing with the `-j=N` (similar to `make` and some other build systems) command-line argument to clangd. ``` $ clangd --help...

Transferred to the clangd repo as this is a server-side issue. Diagnostics about the config file syntax are produced by clangd and communicated over LSP much like diagnostics in C++...

I played around with this a bit, and discovered that clangd does the following which may explain some of the weirdness your user is seeing: * When opening a file...

(I do think the layering here is a bit unfortunate. I think it would be better if the inclusion heuristic were applied at the `InterpolatingCompilationDatabase` level (perhaps it can expose...

> Fixes might include: Treating extension-less files as C++ headers as a fallback (unless some other language has that unfortunate convention). This sounds reasonable to me in principle, but I'll...

> So [based on the logs they posted](https://github.com/hedronvision/bazel-compile-commands-extractor/issues/51), is the issue, we think, that .h headers are also language ambiguous? If so, that might explain why this case came up:...