microsoft / microsoft/vscode-cpptools

constexpr destructors not recognized

Open
#7,965 4 comments 0 reactions 1 assignee View on GitHub

@michelleangela is already working on this.

Since Sep 10, 2021.

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

Description

Bug type: Language Service

Describe the bug

  • OS and Version: Windows 10 Pro 20H2
  • VS Code Version: 1.59.0
  • C/C++ Extension Version: 1.5.1
  • Other extensions you installed (and if the issue persists after disabling them): None
  • If using SSH remote, specify OS of remote machine: -
  • A clear and concise description of what the bug is, including information about the workspace (i.e. is the workspace a single project or multiple projects, size of the project, etc):

main.cpp:

struct Foo
{
    constexpr ~Foo() { }  // when you comment this out, everything is fine
};

constexpr auto cfoo = Foo();  // "Foo::~Foo" not defined
auto foo = Foo();            // this is ok though

int main()
{
    return 0;
}

When I put a custom constexpr destructor in a class, as C++20 now allows us to do, Intellisense says it were not defined.

To reproduce, use above code.

GCC 10.2 (both from recent Mingw and from the Gnu Arm Embedded Toolchain) compiles this code without issues.

Expected behavior is that Intellisense would not issue an error here.

settings.json:

{
    "C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools"
}

No other files present, except for an CMakeLists.txt

cmake_minimum_required(VERSION 3.13.1)
project(FooExample VERSION 0.1.0)

set(CMAKE_CXX_STANDARD 20)
set(CMAKE_CXX_EXTENSIONS OFF)

add_executable(app)

target_sources(app PRIVATE
    "main.cpp"
)

I used cmake 3.17.5 to configure and Ninja to build.

Screenshot: (my Intellisense is in german though)
FooExample

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.