References on the destructor collapse to the whole type, or no results

[lukka]

Environment

cpptools — References on the destructor mv::Vec2::~Vec2() collapse to the whole type

Field	Value
Symbol (spec id)	dtor-Vec2
Declaration	~Vec2(); (destructor)
Query position 1	src/mathvec.h:15:6 (cursor on Vec2, immediately after the ~)
Query position 2	src/mathvec.h:15:5 (cursor on the ~, immediately before Vec2)
Affected LSP request	textDocument/references
Repro archive	P1-dtor-Vec2.zip (this folder)

Summary

For query position 1

Find All References on the destructor of mv::Vec2 returns every mention of the Vec2 type instead of the two destructor sites — even though the cursor is on the destructor name after the tilde. Observed in VS Code with the C/C++ extension (cpptools).

For query position 2

Find All References on the destructor of mv::Vec2 returns no results. Observed in VS Code with the C/C++ extension (cpptools).

Environment

• Editor: Visual Studio Code 1.33.5
• Extension: C/C++ (ms-vscode.cpptools), default IntelliSense engine
• Language standard: C++20 (freestanding fixture; no STL/toolchain required)

Steps to reproduce

1. Extract P1-dtor-Vec2.zip and open the cpp-project folder in VS Code (C/C++ extension enabled).
2. Optionally configure with CMake Tools (preset cdb); the fixture also parses under default C++20 IntelliSense.
3. Open src/mathvec.h and place the cursor either immediately after the ~ in ~Vec2();, on Vec2 (line 15, col 6); or immediately before the ~, on the tilde itself (line 15, col 5).
4. Invoke Find All References (Shift+Alt+F12).

Expected vs actual

Source	Result count
Expected (both positions)	2
cpptools — query position 1	39
cpptools — query position 2	0

Expected (2): the declaration (mathvec.h:15) and the out-of-line definition (mathvec.cpp:11, Vec2::~Vec2()).

Actual — query position 1 (39): every occurrence of the Vec2 type (the same 39-item set as the constructor queries). Placing the cursor after the ~ does not restrict the query to the destructor — it collapses to "all mentions of the type."

Actual — query position 2 (0): no results at all.

Why it matters

Destructor references are used to reason about lifetime and teardown. Returning the whole type population makes that impossible and is especially surprising given the cursor is unambiguously on the destructor.

Bug Summary and Steps to Reproduce

Small repro soruce code:
P1-dtor-Vec2.zip