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

Use more precise wording for errors specifying requirements for types that can be used in a using statement. #74311

Merged
merged 1 commit into from
Jul 12, 2024

Conversation

AlekseyTs
Copy link
Contributor

Closes #73559.

@AlekseyTs AlekseyTs requested review from jjonescz and cston July 9, 2024 15:51
@AlekseyTs AlekseyTs requested review from a team as code owners July 9, 2024 15:51
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Jul 9, 2024
@AlekseyTs
Copy link
Contributor Author

@cston, @dotnet/roslyn-compiler For the second review

Copy link
Member

@jcouv jcouv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Thanks (iteration 1)

@jcouv jcouv self-assigned this Jul 9, 2024
@AlekseyTs AlekseyTs merged commit e231014 into dotnet:main Jul 12, 2024
28 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Jul 12, 2024
@RikkiGibson RikkiGibson modified the milestones: Next, 17.12 P1 Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers New Feature - RefStructInterfaces untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider adjusting wording for ErrorCode.ERR_NoConvToIDisp
4 participants