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

Handle property without accessors in Binder.ReceiverIsSubjectToCloning #70009

Merged
merged 1 commit into from
Sep 21, 2023

Conversation

jjonescz
Copy link
Member

Fixes #69997.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead labels Sep 19, 2023
@jjonescz jjonescz marked this pull request as ready for review September 19, 2023 12:41
@jjonescz jjonescz requested a review from a team as a code owner September 19, 2023 12:41
Copy link
Contributor

@AlekseyTs AlekseyTs left a comment

Choose a reason for hiding this comment

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

LGTM (commit 1)

@jjonescz jjonescz merged commit da52694 into dotnet:main Sep 21, 2023
25 checks passed
@jjonescz jjonescz deleted the 69997-ReceiverIsSubjectToCloning-NRE branch September 21, 2023 08:14
@ghost ghost added this to the Next milestone Sep 21, 2023
@Cosifne Cosifne modified the milestones: Next, 17.8 P3 Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers 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.

NRE from ReceiverIsSubjectToCloning while working in Roslyn.sln
4 participants