[feature request] Provide detailed completion configurations and some enhancements.

[FlyinCow]

I switch to clangd from ms-vscode.cpptools due to its significant performance issue, but it seems clangd does not have a detailed auto-completion configurations. This leads to some confliction to my code habit, and some behaviours are kind of annoying.

Examples:

ex1

If I accept this suggestion there will be brackets after class name, but I just want the class name only

ex2

I implement this class completely in a namespace, but when using delegating constructors clangd still provides namespace::

ex3

C_Cpp.autocompleteAddParentheses is a sweet option, but in clangd this is enforced open.

ex4

It seems there's some compatibility issue with MSVC, codes are compileable but clangd complains. For example, clangd complains that std::runtime_error is not a member of std with #include<excetion>. I do know that I should #include<stdexcept> but this code can be built without any warnings/errors.

[FlyinCow]

Another enhancement is, clangd doesn't support fuzzy matching in auto suggestion. Is this due to performance consideration?

[HighCommander4]

Examples:

ex1

If I accept this suggestion there will be brackets after class name, but I just want the class name only

In clangd 20, this behaviour can be achieved by adding the following to your .clangd config file:

Completion:
  ArgumentLists: None

ex2

I implement this class completely in a namespace, but when using delegating constructors clangd still provides namespace::

Could you file this as a separate issue with a complete code example please?

ex3

C_Cpp.autocompleteAddParentheses is a sweet option, but in clangd this is enforced open.

ex4

Using ArgumentLists: None as mentioned above with prevent this as well.

It seems there's some compatibility issue with MSVC, codes are compileable but clangd complains. For example, clangd complains that std::runtime_error is not a member of std with #include<excetion>. I do know that I should #include<stdexcept> but this code can be built without any warnings/errors.

Please file this as a separate issue, with a code example and clangd logs.

Another enhancement is, clangd doesn't support fuzzy matching in auto suggestion. Is this due to performance consideration?

We do have some fuzzy matching. Can you give an example of what you expect to work but doesn't?

[FlyinCow]

Examples:

ex1

If I accept this suggestion there will be brackets after class name, but I just want the class name only

In clangd 20, this behaviour can be achieved by adding the following to your .clangd config file:

Completion:
  ArgumentLists: None

ex2

I implement this class completely in a namespace, but when using delegating constructors clangd still provides namespace::

Could you file this as a separate issue with a complete code example please?

ex3

C_Cpp.autocompleteAddParentheses is a sweet option, but in clangd this is enforced open.

ex4

Using ArgumentLists: None as mentioned above with prevent this as well.

It seems there's some compatibility issue with MSVC, codes are compileable but clangd complains. For example, clangd complains that std::runtime_error is not a member of std with #include<excetion>. I do know that I should #include<stdexcept> but this code can be built without any warnings/errors.

Please file this as a separate issue, with a code example and clangd logs.

Another enhancement is, clangd doesn't support fuzzy matching in auto suggestion. Is this due to performance consideration?

We do have some fuzzy matching. Can you give an example of what you expect to work but doesn't?

I'll file seperated issues later for ex2 and ex4. As for last issue:


It dose have fuzzy matching but kind of strange for me. When I hit f t I thought clangd would match namespace fmt first but it didn't match it at all. When I hit f t p I thought clangd would match fmt::println (according to Lexicographic order) but there was even no pop-up window at all.

[HighCommander4]

When I hit f t I thought clangd would match namespace fmt first but it didn't match it at all. When I hit f t p I thought clangd would match fmt::println (according to Lexicographic order) but there was even no pop-up window at all.

Thanks, I understand now.

I believe the current fuzzy matching rules break symbol names down into words/segments (e.g. false_type into false and type), and only match the beginnings of the segments, rather than any subsquence. This is why ft matches false_type but not fmt.

There are some issues on file about relaxing fuzzy matching: clangd/clangd#37, clangd/clangd#1236, clangd/clangd#2196.