isolated/owned would solve many problem we face right now.

[Sönke Ludwig]

Am 11.10.2013 23:06, schrieb deadalnix:
> On Friday, 11 October 2013 at 20:55:00 UTC, Sönke Ludwig wrote:
>> Also see:
>> http://forum.dlang.org/thread/k7j1ta$2kv8$1@digitalmars.com
>> http://forum.dlang.org/thread/k831b6$1368$1@digitalmars.com
>>
>> http://vibed.org/api/vibe.core.concurrency/makeIsolated
>> http://vibed.org/api/vibe.core.concurrency/lock
>>
>> The last two links point to a working library based implementation
>> that I have been experimenting with in the vibe.d. It already provides
>> a lot of the possible advantages, but with additional language support
>> it could be made really seamless and safe.
>
> Ha, I remembered that someone did a lib implementation, but couldn't
> remember who.
>
> The lib implementation has some serious flaw when it come to safety, but
> this is already better than nothing !

I agree, it's a lot better than nothing, but it's main purpose should be 
to gather experience for an integrated solution (I could live with a 
partially integrated library solution if safety can be guaranteed, i.e. 
no 'cast' or 'assumeX' overrides are necessary). Another related ^point 
is that we need a better implementation of 'scope', currently it doesn't 
really guarantee anything (although it's still good to have).