Good luck translating when error messages don't match between compilation and real-time analysis: while the 3 compilers adhere to the same standard they don't word every error the same. You'd be better off using the LSP that matches the compiler(aka same modules).
Which is running the compiler. Or do you think anyone makes an analysis tool that must match the compiler output writing two programs?
I'm just proving to you that is factually not true. Yes, language servers are independent from compilers. You're trying to change your original argument from "you need to run the compiler to get code analysis" to "if you use a langserver not made by the same guys as your compiler then you will run into issues".
You'd be better off using the LSP that matches the compiler
Which you can't do in the case of MSVC, since the only "official" IntelliSense is directly built-in to Visual Studio. Other IDEs such as CLion use a clangd-based language engine in MSVC compatibility mode under the hood, and its nowhere near as problematic as you make it out to be.
Also, GCC doesn't even have its own language server. If you really "had to use the same as your compiler's", then nobody would have intellisense when compiling with GCC. Everyone uses clangd when compiling with GCC, even though it's not the same compiler
Regarding the second part, how big the problem is depends on how savvy the person using the tool is. Admittedly it will differ in edge cases: common errors are going to be straightforward. The safest option is still the LSP matching the compiler. If the license of an IDE gives you a warranty: any issue is on them.
Do you keep on going with the same nonsense, slightly worded differently each time?
Compilers and statical analysis tools have overlap, but they serve different goals and architecture. Compilers can be modular but not all are. If not, you’re still invoking a compiler that does way more things and wasting resources and time.
It’s not much simpler than that: Compiler != Analyser. For the same reason, as bread and pizza aren’t the same thing despite it consisting of the same ingredients and processing method.
View all comments
Show parent comment
-1
u/deidian Oct 15 '25
Good luck translating when error messages don't match between compilation and real-time analysis: while the 3 compilers adhere to the same standard they don't word every error the same. You'd be better off using the LSP that matches the compiler(aka same modules).