dotnet/roslyn

Error when binding generic method inside cref when parens and parameters are included in the signature

Open

#2,189 opened on Apr 22, 2015

View on GitHub
 (2 comments) (0 reactions) (1 assignee)C# (20,414 stars) (4,257 forks)batch import
Area-CompilersBughelp wanted

Description

I am not sure what the correct behavior is for the below. But the current behavior certainly seems inconsistent.

capture

Contributor guide

Tech stack
csharp
Domain
backenddeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
C# language knowledgeRoslyn API understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate the binding of generic methods in XML documentation cref attributes. Look for code in the Roslyn compiler that handles cref resolution, particularly when generic type parameters and parentheses are included. The screenshot shows an error message; reproduce the scenario and trace the binding logic to identify inconsistencies. There are no linked PRs, so the fix would need to address the underlying issue.