microsoft / microsoft/vscode-cpptools

constexpr destructors not recognized

Aperta
#7,965 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@michelleangela ci sta già lavorando.

Dal 10/9/2021.

bug Language Service Visual Studio
Lingua principale
TypeScript
Stelle
6.2k
Fork
1.7k
Merge medio
14h 46m
PR unite (30g)
61

Descrizione

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

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.