One of the reasons it is so bad in other editors is that I regularly use non-standard include paths (in large quantity), and having to set those up in the editor is an absolute chore. (I also use Python regularly, and the Jedi-based completions were excellent as well, but those are already present in VSCode). I used to use vim with YouCompleteMe, and set it up to find and read compile_commands.json for the current directory, and it gave me the best C++ autocompletion/go-to-definition experience I've ever found in an editor.
I'm the maintainer of the main CMake extension for VSCode, and I've had cmake-server support for a few months now, as well as an extension API which exposes it.Ī lot of the C and C++-related extensions for VSCode have been very poor in terms of releasing regular updates and the kind build system integration that I've wanted for a long time.
0 kommentar(er)
