On Nov 15, 2012, at 7:17 AM, Andrei Alexandrescu <seewebsiteforem...@erdani.org> wrote:
> On 11/15/12 1:08 AM, Manu wrote: >> >> Side note: I still think a convenient and fairly practical solution is >> to make 'shared' things 'lockable'; where you can lock()/unlock() them, >> and assignment to/from shared things is valid (no casting), but a >> runtime assert insists that the entity is locked whenever it is >> accessed. > > This (IIUC) is conflating mutex-based synchronization with memory models and > atomic operations. I suggest we postpone anything related to that for the > sake of staying focused. By extension, I'd suggest postponing anything related to classes as well.
