Sean McManus

Yeah, repro the issue -- it becomes fixed if instead I use ```cpp #undef __SIZEOF_FLOAT128__ ``` I see 3 other i386 defines that might also need to be undefined, but...

There's should a flame icon if clang-tidy is running. However, there is a bug that can randomly cause the flame icon to get stuck, in which case you can check...

@bobbrow It's not clear from the user's report what issue they're hitting and/or if it's related to #8405 or not.

I'm not aware of any generic, cross-language API for providing compiler info. It looks like you're having configuration problems with system headers. Additional logging from running C/C++: Log Diagnostics might...

@cilence Clang diagnostic errors are not currently disablable, other than avoiding running clang-tidy on particular files, perhaps via C_Cpp.codeAnalysis.exclude, or running a Clear code analysis error code action. You could...

Yeah, it sounds like you want to change your build system to not delete the generated headers that are used to compile. You can set "C_Cpp.errorSquiggles" to false, but it's...

@Ben-Voris You may be able to use a forcedInclude file in your local enlistment with ``` #ifdef __INTELLISENSE__ #pragma diag_suppress #endif ```

You should be able to set C_Cpp.enhancedColorization to "Disabled" as a workaround. Something may be causing our semantic token provider to not provided the info it needs or it could...

This is a duplicate of https://github.com/microsoft/vscode-cpptools/issues/9689 -- we're not sure exactly how to repro it yet, but it seems like removing the duplicate files.associations should fix it. Maybe another setting...

Also, I'm seeing "Connection to server got closed. Server will not be restarted" (i.e. cpptools process crash) but that could be completely unrelated...let us know if you have any more...