A few thoughts on std.allocator
Dicebot via Digitalmars-d
digitalmars-d at puremagic.com
Wed May 13 00:12:01 PDT 2015
On Wednesday, 13 May 2015 at 06:23:40 UTC, Brad Anderson wrote:
> On Wednesday, 13 May 2015 at 05:35:18 UTC, Dicebot wrote:
>> On Tuesday, 12 May 2015 at 17:21:04 UTC, Steven Schveighoffer
>>> The one that always comes to my mind is array appending:
>>> immutable int x = new int;
>>> const int y = x;
>>> x ~= 1; // should this lock;
>>> y ~= 1; // should this lock?
>> As per my udnerstanding `shared` should _never_ result in
>> automatic locking or barriers or whatever. It is simply a tag
>> qualfier, with no extra magical semantics.
> Perhaps this is out of date though.
I have a feeling that no one know what shared truly means
anymore. I remember talking about it with Andrei during last
DConf and his explanation was that it is all about creating user
types that encapsulate concurrency internally (+ atomics). I may
remember wrong of course but was no mention of compiler actually
doing anything special for it.
More information about the Digitalmars-d