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

7589-isReadOnlyObject-and-beReadOnlyObject-are-not-consistent-wrt-immediate-objects #7590

Conversation

MarcusDenker
Copy link
Member

1 isReadOnlyObject returns true, but calling #beReadOnlyObject raises an error.

#isReadOnlyObject has an explicit check for this case in the fallback code, we should add the same to #beReadOnlyObject.

fixes #7589

… an error.

#isReadOnlyObject has an explicit check for this case in the fallback code, we should add the same to #beReadOnlyObject.

fixes pharo-project#7589
@MarcusDenker MarcusDenker merged commit ce878ff into pharo-project:Pharo9.0 Oct 26, 2020
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.

#isReadOnlyObject and #beReadOnlyObject are not consistent wrt immediate objects
2 participants