Nathan Ridge

> Perhaps we should relax this, and show name specifiers which are **class names** when they fit into the length limit? (Namespace names seem like noise even if they fit...

> Another idea is, the parameter inlay hints is pretty useful now, how about split the `--inlay-hints` flag into 2 flags, so we could show the parameter inlay hints only....

> ```c++ > foo(/*inlay hint: bar*/ &bar); // it should be omiited. > ``` We do have logic to omit a hint if it matches the argument expression exactly (i.e....

What client are you using? I have some suggestions which apply to the vscode client. If you just want to change the style (e.g. color) of the code in the...

I believe you're running into #1100, a regression in clangd 14 which has been fixed on trunk (with the fix available in the weekly snapshot releases on the [releases page](https://github.com/clangd/clangd/releases)).

> I will wait until LLVM release a fix (probably in LLVM 14.0.6 ?) By default, the fix will appear in LLVM 15. I do sometimes see fixes being backported...

This doesn't look like a clangd-specific issue to me -- clang itself issues both diagnostics when run on the first example.

> Should I post this as an issue with clang instead? Yep, it's probably a good idea to file this at https://bugs.llvm.org/.

Ah, I see, this issue is about the snippet feature. That was not clear to me before, thanks!. Possibly related to #969, which is also about a code edit made...

> So I was wondering if there is a clangd start opthion like --indent 2/4/8 can control autoformat/snippets indent. I think it is more convenient rather than writing a config...