microsoft / microsoft/vscode-cpptools

<type_traits> totally grayed on c++17

Open
#14,384 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

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:
Image Image
Bug Summary and Steps to Reproduce

Bug Summary:

Steps to reproduce:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. 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

Contributor guide

Open the contributing guide

First steps

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

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.

Assessment

Tech stack
cpp, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.