shared - no read/write access

[Rubn]

On Tuesday, 26 March 2019 at 08:35:42 UTC, Kagamin wrote:
> On Monday, 25 March 2019 at 21:04:37 UTC, Rubn wrote:
>> You don't use the type system with thread local data. Using 
>> shared, actually creates global data, not thread local data.
>
> Unqualified types are specified to be thread local, so thread 
> local data is definitely expressed in the type system.

__gshared int a;

See above, you have an unqualified type. Would you say it is 
thread local? Is there any way you can see that it is thread 
local by the type alone? Are there any guarantees that it won't 
be accessed by another thread? An unqualified type is bare, it 
does not provide any thread-safety, you can easy pass it around 
to another thread to be used and cause race conditions.


Anyways back to the original question you avoided:

> Its meaning is to provide guarantee that thread-local data 
> doesn't have threading issues and I posted the proof of its 
> usefulness.

Why do you think "shared" means thread-local data? And then you 
go on to say that it is unqualified types? I shall ask again, do 
you know what thread-local data is ?