microsoft / microsoft/vscode-cpptools

constexpr destructors not recognized

Abierto
#7,965 4 comentarios 0 reacciones 1 asignado Ver en GitHub

@michelleangela ya está trabajando en esto.

Desde el 10/9/2021.

bug Language Service Visual Studio
Lenguaje dominante
TypeScript
Estrellas
6.2k
Forks
1.7k
Merge medio
14 h 46 min
PR fusionados (30 d)
61

Descripción

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

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.