Fix number of additional overloads on lambda parameter's member recommendations #68028
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…for member recommendations
ghost
added
the
Community
dotnet-issue-labeler
bot
added
Area-IDE
untriaged
genlu
removed
the
untriaged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #61343.
The lambda parameter's type was added to the array twice, causing its members to be considered twice too. This resulted in the wrong number of additional overloads being shown in the completion item's tooltip ($2n-1$ instead of $n-1$ ).
This fix makes the addition of the type symbol conditional so that it doesn't appear more than once in the array of type symbols.