Autocomplete fails for templated class/struct

[kbthomp1]

Type: LanguageService

Describe the bug

• OS and Version: MacOS Mojave 10.14.6
• VS Code Version: 1.42.1
• C/C++ Extension Version: 0.26.3
• Other extensions you installed (and if the issue persists after disabling them):
• A clear and concise description of what the bug is.

intelliSense autocomplete fails to deduce type of templated class declared in templated class/function.

To Reproduce

namespace ID {
template <typename T>
struct addingClass {
  public:
    addingClass(T a, T b) : result(a + b) {}
    const T result;
};

template <typename T>
class TemplatedClass {
  public:
    static T add(T a, T b) {
        auto addition = addingClass<T>(a, b);
        auto result = addition.result; // intelliSense provides not provide auto-complete for addingClass::result member
        return result;
    }
};
}

int main() {
    return ID::TemplatedClass<int>::add(-1, 1);
}

Hovering over the addition variable shows auto addition, and line 14 fails to auto-complete the result class member.

Expected behavior

I would expect auto-complete to deduce the class members of the addingClass in the above example.

Screenshots

Additional context

c_cpp_properties.json:

{
    "configurations": [
        {
            "name": "Mac",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [],
            "macFrameworkPath": [],
            "compilerPath": "/usr/local/bin/gcc",
            "cStandard": "c11",
            "cppStandard": "c++17",
            "intelliSenseMode": "gcc-x64",
            "configurationProvider": "vector-of-bool.cmake-tools"
        }
    ],
    "version": 4
}

[Colengms]

Hi @kbthomp1 . I'm able to repro (a minimal version of) your issue in Visual Studio as well. (The C/C++ Extension shares code for IntelliSense with VS). I've opened a bug against VS here: https://developercommunity.visualstudio.com/content/problem/936260/intellisense-instance-of-template-stored-in-auto-d.html

[glingy]

What is the status of this now that the bug report for VS has been deemed low priority and closed?

[sean-mcmanus]

@glingy We're tracking potential priority changes via upvotes to this GitHub issue (thumbs up icon on the original post).

If you have a Microsoft account, you can also re-file the issue on the VS side -- but FYI they have a different system that requires they periodically close the lower priority issues after a certain period of time, so it could just be closed again later on.

[starball5]

Related question asked on Stack Overflow: Why doesn't Intellisense provide suggestions for templates inside templates that use parameters from the outer template?

[ShellScy]

Might be another similar issue in SO: Is it possible for VS code to detect a templated inherited base class member inside the methods of a templated derived class?

[baskuit]

What if addingClass had a specialization that doesn't have the result member. How is the auto-complete supposed to know which specialization to use with only the totally generic T to go off of?

Anyway this seams to have been solved yeah? Atomic constraints on members will affect autocomplete.