Vision for the D language - stabilizing complexity?

deadalnix via Digitalmars-d digitalmars-d at puremagic.com
Fri Jul 15 13:12:50 PDT 2016


On Friday, 15 July 2016 at 18:01:43 UTC, Andrei Alexandrescu 
wrote:
>> Read or write.
>>
>> For const(T) , same thing, but limited to write.
>
> Thanks. Reworked:
>
> "During and after mutating a memory location typed as 
> (unqualified) type T, no thread in the program (including the 
> current thread) is allowed to (a) effect a read of the same 
> location typed as const(T) or immutable(T), or (b) effect a 
> read or write of the same location typed as shared(T)."
>
>
> Andrei

I think the idea is there, but there is still a problem : "During 
and after" do not have any meaning without ordering 
constraint/memory barrier.



More information about the Digitalmars-d mailing list