-
Notifications
You must be signed in to change notification settings - Fork 1.7k
OpenJun 23, 2026
No due date
•Last updated Issues under consideration for upcoming milestones.
55% complete
List view
0 of 111 selected 0 issues of 111 selected
- Status: Not planned (skipped).#6031 In microsoft/vscode-cpptools;
Function prototypes with trailing macros do not display doc comments
Feature: Doc commentsAn issue related to code comments shown in hover, completion, and signature help.An issue related to code comments shown in hover, completion, and signature help.Status: Closed (completed).#8176 In microsoft/vscode-cpptools;Find All (Peek) References UI randomly doesn't work as expected
Feature: Find All ReferencesFind All References, Peek References, RenameFind All References, Peek References, Renameinvestigate: reproThis issue's repro steps needs to be investigated/confirmedThis issue's repro steps needs to be investigated/confirmedStatus: Not planned (skipped).#9312 In microsoft/vscode-cpptools;Detect opening a workspace folder with a symlink on the path and output a warning message
enhancementImprovement to an existing featureImprovement to an existing featureStatus: Not planned (skipped).#9498 In microsoft/vscode-cpptools;- Status: Not planned (skipped).#10016 In microsoft/vscode-cpptools;
Expand error squiggles that start on # or < e.g. for #include <string.h>
Feature: Code AnalysisRelated to integration with clang-tidy, cppcheck, cl.exe /analyze, etc.Related to integration with clang-tidy, cppcheck, cl.exe /analyze, etc.Status: Not planned (skipped).#10032 In microsoft/vscode-cpptools;Fix all clang-tidy warnings still includes fixes that were cleared
Feature: Code AnalysisRelated to integration with clang-tidy, cppcheck, cl.exe /analyze, etc.Related to integration with clang-tidy, cppcheck, cl.exe /analyze, etc.Status: Not planned (skipped).#9973 In microsoft/vscode-cpptools;Renaming browse database does not delete old database
Feature: ConfigurationAn issue related to configuring the extension or IntelliSenseAn issue related to configuring the extension or IntelliSenseStatus: Not planned (skipped).#10158 In microsoft/vscode-cpptools;Creation declaration/definition that targets a new file (or an empty one) has 2 extra newlines if clang-format isn't used
insidersCurrently only repros with our latest Insiders release.Currently only repros with our latest Insiders release.Works in VSSo we'd need to fix it for VS Code to reach parity.So we'd need to fix it for VS Code to reach parity.Status: Not planned (skipped).#10164 In microsoft/vscode-cpptools;Failed to go to competing definitions when function headers are different
Feature: Go to DefinitionAn issue related to Go to Definition/Declaration.An issue related to Go to Definition/Declaration.verifiedBug has been reproducedBug has been reproducedWorks in VSSo we'd need to fix it for VS Code to reach parity.So we'd need to fix it for VS Code to reach parity.Status: Not planned (skipped).#10702 In microsoft/vscode-cpptools;__has_include does not search Xcode framework path
investigate: reproThis issue's repro steps needs to be investigated/confirmedThis issue's repro steps needs to be investigated/confirmedverifiedBug has been reproducedBug has been reproducedStatus: Not planned (skipped).#10840 In microsoft/vscode-cpptools;Add support for CoreGuideLine Checker
Feature: Code AnalysisRelated to integration with clang-tidy, cppcheck, cl.exe /analyze, etc.Related to integration with clang-tidy, cppcheck, cl.exe /analyze, etc.Status: Not planned (skipped).#531 In microsoft/vscode-cpptools;Give more warning messages if paths can't be found
help wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.Status: Closed (completed).#1671 In microsoft/vscode-cpptools;IntelliSense Parse Directory Exclusions
more info neededThe issue report is not actionable in its current stateThe issue report is not actionable in its current statenot reproingWe're not able to reproduce the issue (it's unlikely to get fixed until we find one).We're not able to reproduce the issue (it's unlikely to get fixed until we find one).Status: Closed (completed).#2192 In microsoft/vscode-cpptools;- Status: Closed (completed).#2342 In microsoft/vscode-cpptools;
- Status: Closed (completed).#2359 In microsoft/vscode-cpptools;
compile_commands.json doesn't work with WSL
investigate: reproThis issue's repro steps needs to be investigated/confirmedThis issue's repro steps needs to be investigated/confirmedStatus: Closed (completed).#2510 In microsoft/vscode-cpptools;incorrect clang-format -style formatting
investigate: reproThis issue's repro steps needs to be investigated/confirmedThis issue's repro steps needs to be investigated/confirmedmore info neededThe issue report is not actionable in its current stateThe issue report is not actionable in its current statenot reproingWe're not able to reproduce the issue (it's unlikely to get fixed until we find one).We're not able to reproduce the issue (it's unlikely to get fixed until we find one).Status: Closed (completed).#2524 In microsoft/vscode-cpptools;- Status: Closed (completed).#3114 In microsoft/vscode-cpptools;
- Status: Closed (completed).#2227 In microsoft/vscode-cpptools;
- Status: Closed (completed).#3427 In microsoft/vscode-cpptools;
go to definition incorrect
Feature: Go to DefinitionAn issue related to Go to Definition/Declaration.An issue related to Go to Definition/Declaration.world readyAn issue relating string character encodings, localization translations, etc.An issue relating string character encodings, localization translations, etc.Status: Closed (completed).#3983 In microsoft/vscode-cpptools;Warning: Path is not a file: AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs\usr\bin\gcc, despite IntelliSense working
Feature: ConfigurationAn issue related to configuring the extension or IntelliSenseAn issue related to configuring the extension or IntelliSensehelp wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.Status: Closed (completed).#3825 In microsoft/vscode-cpptools;On Windows, both gcc/clang and MS extensions should be supported in clang mode, instead of switching to msvc mode
Feature: ConfigurationAn issue related to configuring the extension or IntelliSenseAn issue related to configuring the extension or IntelliSenseStatus: Closed (completed).#3387 In microsoft/vscode-cpptools;- Status: Closed (completed).#3768 In microsoft/vscode-cpptools;