Nathan Ridge

I think it makes sense to re-open this one, as I think there is a lot of relevant discussion here.

This would be very challenging to implement. If we tried to make the compiler process both branches of an `#if` during a single compilation, it would run into errors in...

> When I jump into io.h for instance, it says it's not part of the compilation database ... while this is correct technically, I would that included files would kinda...

> I passed "--compile-commands-dir ." to it and it helped, I wonder though why it isn't the default? If you don't pass `--compile-commands-dir`, clangd will, for each open file, look...

> Would you ever want that? `--compile-commands-dir .` would seem to me like the better default, but I might be wrong. There are a few issues here: * I assume...

Do you have a suggestion for where the content of the documentation should come from?

This has come up in https://github.com/clangd/vscode-clangd/issues/452 as well. I suspect it may be intentional, though I don't know the motivation for it. Perhaps some folks who worked on include-cleaner such...

Assuming that an angle include is a system header doesn't seem justified, since, when resolving an angle include, the compiler does look at regular entries of the include search path...

I agree that not respecting `--function-arg-placholders` for lambdas seems like an oversight. Regarding parentheses, there are a couple of related bugs on file: * https://github.com/llvm/llvm-project/issues/63565 is about adding an option...

See also: #527, #1850