microsoft / microsoft/vscode-cpptools
"Go to Definition/Declaration" don't work correctly with the function parameters of a `std::function`
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 6.2k
- Forks
- 1.7k
- Ø Merge
- 14 Std. 46 Min.
- Gemergte PRs (30 T.)
- 61
Beschreibung
Bug type: Language Service
Describe the bug
- OS and Version: Arch Linux, kernel: 5.10.39-1-lts
- VS Code Version: 1.56.2
- C/C++ Extension Version: v1.4.0-insiders3
- Other extensions you installed (and if the issue persists after disabling them): I don't have other enabled extensions from the "C++" category
When I perform the "Go To Definition" or "Go to Declaration" action on a parameter of the function signature in a std::function type, VSCode navigates to the definition/declaration of std::function in the standard library instead of the actual type definition/declaration. Strangely enough, these actions work properly with the return type of the signature.
Steps to reproduce
- Copy the code sample into a
.cppfile. - Right click on the
fooinside the parentheses and choose eitherGo to DefinitionorGo to Declaration. - Observe that VSCode navigates either to the definition of
std::function(ifGo to Definitionwas used) or to its declaration.
Expected behavior
VSCode should navigate to the definition of foo within the same file.
Code sample and logs
- Code sample
#include <functional>
struct foo
{
int bar;
};
using baz = std::function<foo(foo)>;
int main()
{
return 0;
}
- Logs from running
C/C++: Log Diagnosticsfrom the VS Code command palette
-------- Diagnostics - 5/26/2021, 10:46:45 AM
Version: 1.4.0-insiders3
Current Configuration:
{
"name": "Linux",
"includePath": [
"${workspaceFolder}/**"
],
"defines": [],
"compilerPath": "/usr/bin/clang",
"cStandard": "c17",
"cppStandard": "c++14",
"intelliSenseMode": "linux-clang-x64",
"compilerPathIsExplicit": true,
"cStandardIsExplicit": true,
"cppStandardIsExplicit": true,
"intelliSenseModeIsExplicit": true,
"compilerArgs": [],
"browse": {
"path": [
"${workspaceFolder}/**"
],
"limitSymbolsToIncludedHeaders": true
}
}
No active translation units.
------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 52380
Number of files parsed: 6413
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Reproduziere das Problem mit dem bereitgestellten .cpp-Beispiel in VS Code mit der C/C++-Erweiterung; beginne mit Go to Definition oder Go to Declaration auf foo innerhalb von std::function<foo(foo)>. Fertig ist es, wenn beide Aktionen zur Definition von foo in derselben Datei navigieren und nicht zu std::function.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- cpp, vscode
- Bereich
- devtools
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 35/100