Sean McManus

Also, you could run a command line `/usr/bin/clang++-15 -std=c++2b -E ./test.cpp > ./test.out.cpp` to generate a preprocessed file and look for an IntelliSense error that may be the root cause...

With the main2.zip file I hit https://developercommunity.visualstudio.com/t/C-IntelliSense-doesnt-recognize-clang/10156062 , which might be the root cause of this bug, but I'm not sure yet. I don't get the error when I remove...

Also, with the main.zip, I'm getting some "not implemented" error internally -- our C++23 support is still in development so it looks like the system header code is using features...

Ah, okay -- I got the repro now -- I didn't have libc++ installed. I'm investigating... UPDATE: Looks like we aren't handling "-fexperimental-library" sufficiently -- clang itself gives the same...

@Zingam You should be able to work around the issue via using ` "defines": [ "__has_feature(experimental_library)=1"],` I'm not sure yet if the fix will make it into 1.13.1 or not.

Fixed with 1.13.1: https://github.com/microsoft/vscode-cpptools/releases/tag/v1.13.1

@Zingam Okay, I've filed https://github.com/microsoft/vscode-cpptools/issues/9937 to track those issues.

Is using ```json "[cpp]": { "editor.hover.enabled": false } ``` sufficient?

Also, the bad/incorrect hover result is caused by usage of C_Cpp.intelliSenseEngine "Tag Parser" or a configuration error that is causing it to fall back to the "Tag Parser" hover (or...

Setting "C_Cpp.intelliSenseEngine" to "Disabled" will work, but it would disable "all" language service features. The implementation of a new "C_Cpp.hover" setting might follow the example of the existing "C_Cpp.autocomplete" setting.