microsoft / microsoft/vscode-cpptools

mdspan

Open
#11,295 3 comments 0 reactions 1 assignee View on GitHub

@michelleangela is already working on this.

Since Aug 7, 2023.

bug Language Service verified Visual Studio
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Environment
  • OS and Version: Windows 11
  • VS Code Version: 1.82.0-insider
  • C/C++ Extension Version: 1.16.3
Bug Summary and Steps to Reproduce

Bug Summary:
I am trying to use the mdspan in VSCode. I am using the parameters in Godbolt example and made a test. The code compiles without warnings or errors, however, VSCode intellisense shows an error. I have matched the compile flags with VScode c_cpp_properties.json, however, the error still persists.

Steps to reproduce:

  1. Go to 'https://github.com/danchitnis/mdspan-test'
  2. Close and open with VSCode
  3. modify the c_cpp_properties.json, to point to your g++ compiler
  4. See the highlighted errors in VSCode

Expected behavior: No highlighted errors

Configuration and Logs
{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/include"
            ],
            "defines": ["_DEBUG", "UNICODE", "_UNICODE"],
            "cStandard": "c23",
            "cppStandard": "c++23",
            "intelliSenseMode": "windows-clang-x64",
            "compilerPath": "c:/msys64/ucrt64/bin/g++.exe",
            "compilerArgs": [
                "-std=c++23"
            ]
        }
    ],
    "version": 4
}
Other Extensions

No response

Additional context

Errors are:

no instance of constructor "std::extents<IndexType, Extents...>::extents [with IndexType=unsigned long long, Extents=<18446744073709551615ULL, 18446744073709551615ULL>]" matches the argument listC/C++(289) test.cpp(13, 45): argument types are: (int, int)

expression preceding parentheses of apparent call must have (pointer-to-) function typeC/C++(109)

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.