Object is definitely not readonly when VM do not support write barrier. But right now it will be primitive failure.

For example it makes impossible to modify classes in Pharo 7 on ARM VM.
Pharo 7 checks instances for readonly before migrating them

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.