I'm doing template hell. It reports a template error, even though it actually compiles fine.

Environment

Version: 1.84.0-insider (user setup)
Commit: 58bdf2c7c40be6f4494ae35a09528708832cf357
Date: 2023-10-18T05:50:15.982Z
Electron: 25.9.1
ElectronBuildId: 24472542
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045

• OS: Windows 10 22H2
• C/C++ Extension Version: v1.18.0

Bug Summary and Steps to Reproduce

Bug Summary: Incorrect error detector for template hell.

Steps to reproduce:

1. Make a new project, and put this code in: https://godbolt.org/z/f1EadG3dE
2. Wait a bit for IntelliSense to load
3. Go to example.cpp
4. See error
   

Expected behavior: No error reported as it compiles fine(See godbolt).

Configuration and Logs

{
    "configurations": [
        {
            "name": "windows-gcc-x64",
            "includePath": [
                "E:\\include"
            ],
            "compilerPath": "D:\\msys64\\mingw64\\bin\\g++.exe",
            "cStandard": "${default}",
            "cppStandard": "c++23",
            "intelliSenseMode": "windows-gcc-x64",
            "compilerArgs": [
                "-fno-ms-extensions"
            ]
        }
    ],
    "version": 4
}

lslogging.txt

Other Extensions

No response

Additional context

No response

Reproduce the report in example.cpp using the supplied Windows GCC configuration and compare the result with the Godbolt example. Start by reviewing lslogging.txt and the IntelliSense error for the template code. Done means the code continues to compile and IntelliSense no longer reports an error for this reproducer.