Nathan Ridge

Results 1499 comments of Nathan Ridge

> clangd extension version: You left this blank, can you post it please? You can see the version when you hover over the extension in the Extensions panel, for example...

Ok, so that one is a `-Wdeprecated` diagnostic. So, is your suggestion that clangd should send a `Deprecated` diagnostic tag for the `-Wdeprecated` diagnostic, but not for the clang-tidy `modernize-`...

> Does this error have anything to do with the clangd installed on my computer? I found that its version number `13.0.1-++20220120110924+75e33f71c2da-1~exp1~20220120231001.58` looked very strange. Yes, I think the issue...

> Truthfully, though, the main issue with the strikethrough comes from my example of typedef'ed enums, where it obscures important information. And that could probably be solved by changing the...

Not sure if this helps at all, but https://reviews.llvm.org/D154443 downgrades the severity of diagnostics with the `Deprecated` tag to [DiagnosticSeverity.Hint](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#diagnosticSeverity).

Could you attach complete logs please (the snippet you posted does not contain, for example, the `textDocument/publishDiagnostics` message), as well as the source file you have open?

I'm seeing a lot of diagnostics in the system headers, including ones like this: > V[17:43:51.062] Dropped diagnostic: C:/TDM-GCC-64/bin/../lib/gcc/x86_64-w64-mingw32/10.3.0/../../../../x86_64-w64-mingw32/include\stdio.h: '__format__' attribute argument not supported: gnu_printf I wonder if perhaps these...

> And it's only a single file project so I thought using `compile_commands.json` would be an overkill. Yeah, that's understandable. In clangd 16 you can use `--query-driver` without `compile_commands.json`, by...

> The [same problem](https://github.com/clangd/vscode-clangd/issues/419#issuecomment-1331628085) occurs when I Ctrl-click a function to access the library. The "Request XXX failed" errors in the linked screenshot don't seem to be related to this...

One more thought: please include in the patch a change to [CHANGELOG.md](https://github.com/clangd/vscode-clangd/blob/master/CHANGELOG.md) to add a new section at the top titled "Next", and a bullet point under it mentioning this...