shared - no read/write access

[Rubn]

On Wednesday, 27 March 2019 at 18:25:09 UTC, Kagamin wrote:
> On Tuesday, 26 March 2019 at 21:09:18 UTC, Rubn wrote:
>> __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?
>
> It has thread local type. It's an escape provided to ease 
> migration from other languages, when it's difficult for 
> whatever reason to have shared data qualified as shared.

Is it thread local data? How do you identify it is not 
thread-local data by type only (it is unqualified)?

>>> 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?
>
> shared is a qualifier for data that is not thread local, so 
> that thread local data remains unqualified to reduce churn for 
> it.

You have not answered the question.