On 26 March 2018 at 11:26, Chris Muller <asqueaker at gmail.com> wrote:

> On Sun, Mar 25, 2018 at 6:18 PM, Eliot Miranda <eliot.miranda at gmail.com>
> wrote:
> > Hi All,
>
> Hi Eliot,
>
> Congratulations on the enhancement.  As developer of Magma, I'm
> interested in learning more about it as a possible alternative to the
> WriteBarrier.  How does it work?
>
> First, it might help me to understand what _your_ primary motivation
> for proposing to make various entire classes of objects read-only by
> default?
>


But my hope was that this capability would be provided with
> granularity at the object-level, not necessarily the class level.
>

I would presume an entire class is not made read-only by default,
just particular objects formed from literals at compile time.


>     the VM now has support for read only objects, and the first logical
> > application is for literals, making boxed floats, strings, symbols,
> arrays
> > and byte arrays read-only.
>
> Wow, Arrays and ByteArrays too?  Magma's core Buffer classes all use
> ByteArray's internally to represent and update their state.  Ouch!



cheers -ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180326/5a956be6/attachment-0001.html>