Suppress C++17 warnings from LSP client in neovim

Asked May 03 '23 at 10:57

Active May 03 '23 at 11:24

Viewed 375 times

I installed the LSP client for C++ development using the plugin manager "packer" in neovim. My lua config was almost exclusively copied from this website:

LSP in Neovim

When working with modern CPP however, I get warning messages. The native LSP client does not support modern CPP apparently?

For example this line of code uses nested namespaces:

namespace Tuple::Person

The warning message I get looks like this: Nested namespace definition is a C++17 extension; define each namespace separately.

Structured bindings also don't work:

auto [name, age] = Tuple::Person::getPersonData();

The warning message: Decomposition declarations are a C++17 extension.

Does anyone know how to fix this? In case you don't, do you have other recommendations on how to integrate clangd, clangtidy or in general C++ auto completion in neovim? I tried using YouCompleteMe, but that didn't work for me as well. Thanks for any help or recommendations in advance!

edited May 03 '23 at 11:24

asked May 03 '23 at 10:57

Eldinur the Kolibri

1

You may get better, faster feedback on how to configure it for C++17 if you ask on the LSP discussion forums. – Eljay May 03 '23 at 11:43
1

@Eljay Thanks. Where are those discussion forums? As you can see... I'm a new contributor.. :) – Eldinur the Kolibri May 03 '23 at 11:45
In the link you provided, click on the link within that where it mentions "discussion tab" on github. – Eljay May 03 '23 at 11:46
What LSP server is this? Clangd? – HolyBlackCat May 03 '23 at 13:11
yes exactly.... – Eldinur the Kolibri May 03 '23 at 14:26
Do you have a compile_flags.txt or compile_commands.json file? You can set -std=c++17 in there and it should work. – cigien May 03 '23 at 15:29
@cigien No, this is not what I meant.. In the editor itself (nvim), there are warnings visible. Using g++ 12.2.0 compiling C++23 is not a problem. No warnings occur there.. – Eldinur the Kolibri May 03 '23 at 17:22
2

That's what I mean. The neovim lsp will look for the appropriate compilation commands in specific places, e.g. compile_flags.txt. Try adding this file and see if it works. – cigien May 04 '23 at 09:40
@cigien You're right. It was as easy as that! Thanks ;) – Eldinur the Kolibri May 06 '23 at 09:26

Suppress C++17 warnings from LSP client in neovim

0 Answers0