Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IntelliSense reports different number of overloads than signature help #23948

Open
Suchiman opened this issue Dec 27, 2017 · 2 comments
Open

Comments

@Suchiman
Copy link
Contributor

Suchiman commented Dec 27, 2017

Version Used: VS 15.5.2

Steps to Reproduce:

  1. Go to this line of code
    return obj is UsedNamespaceOrType && base.Equals((UsedNamespaceOrType)obj);
  2. Hover base.Equals and Quick Info suggests there's one additional overload
    image
  3. Prompt Signature Info and it only shows one overload
    image

Expected Behavior:
When Quick Info displays (+1 overload) then Signature Info should show exactly 2 overloads

Actual Behavior:
Signature Info may show less overloads than Quick Info suggests there are.

@sharwell
Copy link
Member

sharwell commented Dec 27, 2017

Duplicate of #22341

This seems to be a slightly different cause, but very similar to the above bug.

@sharwell sharwell marked this as a duplicate of #22341 Dec 27, 2017
@sharwell sharwell added the Resolution-Duplicate The described behavior is tracked in another issue label Dec 27, 2017
@sharwell sharwell reopened this Dec 27, 2017
@sharwell sharwell removed the Resolution-Duplicate The described behavior is tracked in another issue label Dec 27, 2017
@jcouv jcouv added the Area-IDE label Dec 27, 2017
@Suchiman
Copy link
Contributor Author

@sharwell at least in the same direction, i believe the bug here is with Quick Info and Signature Info is correct, i'm not sure where Quick Info is getting that additional overload from... perhaps the static object.Equals(Object objA, Object objB)
Even if you clear it to base.Equals() Signature Info still shows only one overload.

@jinujoseph jinujoseph added this to the Unknown milestone Jan 8, 2018
@jinujoseph jinujoseph added the Bug label Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants