Want reasonable reference counting? Disable automatic sharing of immutable

Timon Gehr timon.gehr at gmx.ch
Mon Nov 15 15:23:25 UTC 2021


On 15.11.21 15:27, deadalnix wrote:
> On Monday, 15 November 2021 at 12:24:33 UTC, Timon Gehr wrote:
>> On 15.11.21 11:36, rikki cattermole wrote:
>>>
>>> On 15/11/2021 10:28 PM, Danni Coy wrote:
>>>> that feels like a single object from a user perspective?
>>>
>>> The most important thing about this is: it'll all be in continuous 
>>> memory.
>>>
>>> Perfect for all of your crashing needs due to read only memory!
>>
>> Whoever allocates the object knows the memory layout and can put it in 
>> writable memory.
> 
> If the object is allocated, it HAS TO BE in mutable memory.

No, you can allocate it on the GC heap in CTFE and then store it in the 
immutable data segment at runtime by assigning to a static immutable 
variable.

In general, you can allocate first and then change the protection 
attributes on the page later.


More information about the Digitalmars-d mailing list