coc-clangd VS include-what-you-use

C/C++/Objective-C

I use coc.nvim with coc-clangd

I am currently using coc-clangd(https://github.com/clangd/coc-clangd) for c++ syntax highlighting. I use for coding sometimes, and I get an error because is only g++ header, not for clang. What should I do?

Using this plugin I have installed several extensions like coc-clangd and coc-rust-analyzer .

I don’t mean to be rude but, what about checking ‘configuration’ section: https://github.com/clangd/coc-clangd

use plugins. I prefer coc.nvim paired with coc-clangd Clangd is what CLion uses under-the-hood for a lot of its autocomplete/linting/etc., so this pair gets you fairly close. (you miss out on CLion's proprietary additions and AI completion, but for quick work or places CLion is too heavy, its great)

Not sure about setting up on OpenVMS, but I've been getting along with simple C/C++ projects with coc-clangd which was very easy to set up.

I forgot to mention before, with coc.vim, you will need https://github.com/clangd/coc-clangd to integrated c++

Thanks! I read about using LSP/Clangd with vim via [coc](https://github.com/clangd/coc-clangd) and I think that's the path I'll try going down.

Other responses, thanks for your input. Just want to clarify that I have tried VS and VSCode with limited success (sometimes search works, sometimes it doesn't, and my biggest gripe is an occasional lack of transparency into what's going on under the cover).

Interesting...how does it compare to https://github.com/include-what-you-use/include-what-you-use ?

Build Insights in Visual Studio, include-what-you-use).

Looks like https://include-what-you-use.org/ might do that.

If you are worried about includes, use https://github.com/include-what-you-use/include-what-you-use and stop thinking about it.

Getting rid of that is not straightforard, though some tools can help with that

You can use the tool https://github.com/include-what-you-use/include-what-you-use to do this for for. It tracks included files and can give comment for what is used from each file. It also warns you when you include files that you don’t use

Invisible imports (e.g. traits). In Python, everything is fully namespaced (unless you from import * in which case all bets are off). It's always explicit where a name is coming from. C is the opposite: #include lets you refer to anything defined in the headers with no namespacing. That's why a common strategy (include what you use) has an associated code style: after every non-std #include you have a comment saying which of its definitions you are using. Of course, Rust is much less implicit, but I still sometimes struggle with traits. For example, you can use tokio::net::TcpStream, but you need to also use tokio::io::AsyncReadExt for the .read trait to be defined on TcpStream. This makes it hard (for me) to answer questions like "what traits are currently available in this scope?" and "why is this module being imported?"

Aside from being closed source and not available on all architectures, how does it compare to iwyu(https://include-what-you-use.org/) or clang's relatively recent include-fixer which is also accessible via clangd?

I set up include-what-you-use and I let it tell me which headers should be where. The IWYU rules would have put all needed headers including in the cpp file.