5 ms·
C++ modules still not supported on VSCode, always pissed when I get notifications from this 5 y.o. thread [0]. 0: https://github.com/microsoft/vscode-cpptools/
by Toritori12 1y ago
C++ modules still not supported on VSCode, always pissed when I get notifications from this 5 y.o. thread [0].
0: https://github.com/microsoft/vscode-cpptools/issues/6302 https://github.com/microsoft/vscode-cpptools/issues/6302
- IshKebab 1y agoDoes Clangd support it? It's much better than Microsoft's C++ extension - and open source!
- jpc0 1y agoYes this. Clangd-19 which is current stable has very good support for modules. The only issues I’ve encountered is with import std; which quite honestly is bleeding edge. Your tooling (clangd+cmake) has to be pretty modern t those two are also the easiest to just upgrade since it’s dev time only. And obviously if it’s a discussion you have a C++20 compatible compiler. I’m happily using modules with gcc-14, clangd 19 and cmake 3.28 other than clangd 19 those are just packages you can install in Ubuntu 24.04 which is over a year old at this point.
- pjmlp 1y agoVisual Studio and Clion are the ones currently with the best experience regarding modules. And in VS could be much better, but EDG has other priorities. VSCode isn't really that great option for C/C++.
- m-schuetz 1y agoI prefer vscode simply because VS is excruciatingly slow. e.g. the file open pane in vscode pretty much instantly lists the file I'm looking for, while the counterpart in VS (ctrl+,) takes several seconds and intermixes search results for files and file contents, when I'm only interested in files.
- NotCamelCase 1y ago> VS (ctrl+,) takes several seconds and intermixes search results for files and file contents, when I'm only interested in files. I hate this a lot. It's gotten so bad the last couple of releases to the point that I try and use VS Code more in lieue of VS except debugging. How they could let such fundamental functionality get broken is beyond me.
- Toritori12 1y agoSame here, those "mini" delays are not worth.
- pjmlp 1y agoCtrl+, followed by f filename, you will get the file. The only reasons I use VSCode are the plugins I cannot get on VS, like Powershell, Rust, Azure tooling, and for stuff like Next.js, better use an editor that is anyway a browser in disguise. Performance has never been a part of my decision flowchart.
- m-schuetz 1y agoI know it gets you the file...after several seconds. Vscode gives it instantly. I use this feature so often, it's basically a dealbreaker for VS. I keep both editors open, but VS is basically just there to hit the compile button and for the occasional debugging.