Improve CS0119 error documentation with specific guidance for Type collections #47308
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.
Enhanced the CS0119 compiler error documentation to address user feedback about uninstructive error messages when working with collections of types.
Problem
Users encountering CS0119 when trying to create
List<Type>collections found the existing documentation too generic and unhelpful. The original issue described a scenario where a developer attempted:The existing documentation only provided a generic example about method/class naming conflicts, leaving developers without clear guidance on how to properly work with type collections.
Solution
Added a comprehensive Example 2 that specifically demonstrates:
List<Type>typeof()operatorType.GetType()The new example includes:
Impact
Developers encountering CS0119 in this common scenario will now have:
Fixes #26433.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.
Internal previews