Skip to content

Do not allow sideeffects when readonly property modification fails #10757

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

Merged
merged 3 commits into from
Mar 3, 2023

Conversation

kocsismate
Copy link
Member

Related to #10389 (comment)

@kocsismate kocsismate requested a review from iluuu1994 March 3, 2023 10:24
@kocsismate kocsismate force-pushed the readonly-clone-reinit-fix branch from de450d7 to 0f1d26f Compare March 3, 2023 10:25
@kocsismate kocsismate changed the title Do not allow possible sideeffects when readonly property modification fails Do not allow sideeffects when readonly property modification fails Mar 3, 2023
Copy link
Member

@iluuu1994 iluuu1994 left a comment

Choose a reason for hiding this comment

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

LGTM. Just some styling nits where we're relatively consistent.

@kocsismate kocsismate force-pushed the readonly-clone-reinit-fix branch from 0f1d26f to ebe358c Compare March 3, 2023 12:13
@kocsismate kocsismate merged commit e053ba0 into php:master Mar 3, 2023
@kocsismate kocsismate deleted the readonly-clone-reinit-fix branch March 3, 2023 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants