Go to Definition (F12) will list many redundant files

[gtianw]

Environment

• OS and Version: Windows_NT x64 10.0.19045
• VS Code Version: 1.100.2 (system setup)
• C/C++ Extension Version: 1.25.3
• If using SSH remote, specify OS of remote machine: WSL2, Ubuntu20.04

Bug Summary and Steps to Reproduce

Bug Summary:
Go to Definition will list many redundant files.
These files are not included by CMakeLists.txt or compile_commands.json.
duplicates #11887, but it is no longer active.

Steps to reproduce:

1. Download code from https://github.com/gtianw/Issue/tree/cpptools/13660
2. F12 or Ctrl+LeftClick on target_prt.

Expected behavior:
Only parse the file included by CMakeLists.txt or compile_commands.json, and directly jump to function definitions.

[gtianw]

In a real project, there may be dozens of targets.

[sean-mcmanus]

@gtianw It looks like this is caused by the parent folder of main.cpp being the workspaceFolder root, so both CMake Tools and compile commands are recursively parsing the workspaceFolder for symbols. I believe that is "by design" but it's possible we could implement some design change. You could potentially use

    "C_Cpp.files.exclude": {
        "**/target2": true,
        "**/target3": true
    }

@Colengms might have additional workaround suggestions.

[gtianw]

I will switch between multiple targets according to the usage scenario, and very frequently, so C_Cpp.files.exclude is not suitable.

[sean-mcmanus]

@gtianw Are you able to not have the parent folder be used, i.e. by not having any source files at the root?

[sean-mcmanus]

@gtianw Otherwise, did you have some sort of design change in mind (that doesn't break existing user scenarios) to prevent files at the rule from causing recursive tag parsing of all the subfolders?

[gtianw]

@gtianw Are you able to not have the parent folder be used, i.e. by not having any source files at the root?

I tried, but the problem persists.

[gtianw]

@gtianw Otherwise, did you have some sort of design change in mind (that doesn't break existing user scenarios) to prevent files at the rule from causing recursive tag parsing of all the subfolders?

Maybe add a new option in c_cpp_properties.json, similar to limitSymbolToIncludeHeaders. When this option is enabled, only included files are parsed.
It would be better if there was a global option that each Configuration name inherited by default.