vscode-clangd VS vscode-cpptools

Thanks for your reply, maybe I should go to vscode-clangd community to try to find out how they implement this:)

But I will say that I am mostly happy with either one of the clangd and ccls plugins. The clangd plugin is nicely packaged with a self-installer. The ccls plugin takes a little more work to set up, but it has loads more features. Both are quite good at working with a proper AST. Both build the AST by actually compiling your code with libclang (llvm's compiler core). Both work reliably for me because I am able to provide a compile_commands.json using my project builder (ninja). Nice as it is, it does not update automatically, and I'm not sure I want it to.

For C# there is https://github.com/muhammadsammy/free-omnisharp-vscode for Python there is https://github.com/Microsoft/pyright (Pylance is the proprietary counterpart) for C++ there is https://github.com/clangd/vscode-clangd

Now if only MS would fix VSCode[0] :'(. Come on, the feature if more than half a decade old and this point.

0: https://github.com/microsoft/vscode-cpptools/issues/6302

🔗 Link to GitHub Issue: Add Similar Function - https://github.com/microsoft/vscode-cpptools/issues/11477

According to this: https://github.com/microsoft/vscode-cpptools/issues/3423 it seems to be at least somewhat possible to reuse natvis files from Visual Studio, but I have not tested that. Never really had the need to look at any non-vector container in the debugger.

Thank you for the feedback! Perf is always an ongoing issue for us but I can say that we’ve recently allocated one of our senior engineers to take on more perf related issues. Something that really helps us out is if you could file reproducible steps that lead to your performance issue. This allows us to address the issues more readily. Please file your issues here: https://github.com/microsoft/vscode-cpptools/issues

Yes, see this github issue for an example: Add Ada to supported languages for debugging · Issue #10475 · microsoft/vscode-cpptools (github.com)

Nope https://github.com/microsoft/vscode-cpptools/issues/16

and finally, it you're not happy using the extension I provided you, try fo contact the C/C++ Extension repo on GitHub, they'll help you out with your issue. Here's the link: https://github.com/microsoft/vscode-cpptools

Vous devez définir le nom de votre exécutable dans launch.json. Ils expliquent ce qu'il faut faire et comment ici : https://github.com/Microsoft/vscode-cpptools/blob/master/launch.md