Nathan Ridge

The status bar showing "Parsing includes" as you're typing is expected, as clangd reparses the file in response to the edits you're making. I'm also not seeing anything out of...

> @HighCommander4 Shall we transfer this issue to the server repo? Transferred.

Some other bugs we have on file about code involving large arrays: #967, #1087 .

Please feel free, I probably wouldn't get to this for a while :)

It's a good question. Usually, the way this would work is that the [client capabilities](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#inlayHintClientCapabilities) include an option that indicates whether the client supports the richer format. However, since there...

I think the idea behind having an **array** of `InlayHintLabelPart`s is that for a hint like `std::vector`, we can have four label parts: `std::vector`, ``, with the `std::vector` and `C`...

It would be handy if there existed a version of `TypePrinter` that printed the type into a virtual buffer that could be referenced via `SourceLocation`s, and also constructed a `TypeLoc`...

`ExplicitReferenceCollector` is not really useful for us in the absence of a way to get a `TypeLoc` for the type, because it operates on AST nodes that have associated `SourceLocation`s,...

@zyn0217 what do you think about making some incremental progress here by starting with a simple initial change, e.g. always producing just one `InlayHintLabelPart` for a type hint which takes...

> is there a way to index and link all the files in the project from the compilation database? That should happen by default. The log might contain clues as...