IntelliSense-based Go to Definition returns both const and non-const methods as results (instead of just the matching one)

After the fix for #3014 ships.

struct foo
{
int func() const; // These are defined in a different .cpp file.
int func();
};

int main()
{
foo f;
f.func(); // Go to def doesn't take the const-ness into account and returns both.
}

This seems too low priority to worry about currently. If anyone wants this fixed, upvote it.

The following issue may be related. The scenario is not typical as user would not do a "go to definition" on a definition.

Sample code:

int func1(); // declaration
int func1(float var1) // local param
{
    {
        double var1 = 0; // new local scope
        return var1;
    }
    return var1 + func1();
}

int func1() // overload. Returns confirmed and non-confirmed references.
{
    if (var1 == 0)
        return func1(0);
}

Do a "Go to definition" on definition of int func1(float var1)
It returns two results instead of just staying at the definition.

Does it return two results because it's an overloaded function?

Michelle Matias (@michelleangela)

Michelle Matias (@michelleangela) I think it's doing a Find All References. I think you can change the behavior via changing editor.gotoLocation.alternativeDefinitionCommand.

The original issue appears to be fixed now.

Navigation Menu

Repository navigation

IntelliSense-based Go to Definition returns both const and non-const methods as results (instead of just the matching one) #3015

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

IntelliSense-based Go to Definition returns both const and non-const methods as results (instead of just the matching one) #3015

Description

Activity

michelleangela commented on Jul 14, 2021

sean-mcmanus commented on Jul 15, 2021

bobbrow commented on Nov 27, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions