<type_traits> totally grayed on c++17

Open

#14,384 opened on Apr 16, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Quiet
Tech stack: cpp, vscode
Domain: devtools

Research direction

Start by reproducing the report in VS Code with the supplied c_cpp_properties configuration and the C++17 standard, focusing on how <type_traits> is displayed. Compare the IntelliSense behavior with the expected header state; done means the standard header is no longer incorrectly grayed under this configuration.

Written by the indexing model from the issue text.

Description

Environment

OS and Version: Ubuntu 22.04
VS Code Version: 1.107.1
C/C++ Extension Version: 1.31.4
If using SSH remote, specify OS of remote machine:

Bug Summary and Steps to Reproduce

Bug Summary:

Steps to reproduce:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior:

Configuration and Logs

{
    "configurations": [
        {
            "name": "gcc",
            "includePath": [
                "${workspaceFolder}/**",
                "/usr/include/gtk-3.0",
                "/usr/include/gtk-3.0/gtk",

                "/usr/include/glib-2.0",
                "/usr/include/glib-2.0/glib",
                "/usr/lib/x86_64-linux-gnu/glib-2.0/include",
                "/usr/include/atk-1.0/atk",
                "/usr/include/atk-1.0",
                

        "/usr/lib/gcc/x86_64-linux-gnu/11/include/**",
          "/usr/include/i386-linux-gnu/asm",

         "/usr/include/**"
      

            ],
            "defines": [],
            "compilerPath": "/usr/bin/g++",
            "cStandard": "c17",
            "cppStandard": "c++17",
            "intelliSenseMode": "linux-gcc-x64"
        }





    ],




    
    "version": 4
}

Other Extensions

No response

Additional context

No response

Dominant language: TypeScript
Stars: 6.2k
Forks: 1.7k
Avg merge: 14h 46m
Merged PRs (30d): 61

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

IntegrationStore's ?workspace search param has no reader since the plugin removal Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

ontola/atomic-server#1625 · Opened Sep 22, 2026
O inbox se expande quando clica no chat de conversa que tenha algum código grande exemplo ( chave pix etc) Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

melgarafael/DeskcommCRM#1451 · Opened Sep 22, 2026
Hikvision native Two Way Audio sends no audio: request() drops the body argument Open

Difficulty 1/5 Under an hour Newbie friendliness 82/100

koush/scrypted#2156 · Opened Sep 22, 2026
[Bug]: Refused merge tells you to check write access when the branch only needs a review Open

bug via-triage

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

pingdotgg/t3code#13065 · 1 comment · Opened Sep 22, 2026
feat(compact-js): thread the optional execution clock (time) through ExecutionContextParams Open

bot:ai-assisted component:compact-js status:untriaged

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

midnightntwrk/midnight-sdk#403 · Opened Sep 22, 2026

More TypeScript issues