Re: std.signals regressions - std.signals2

2013-06-17 Thread David
Am 17.06.2013 22:23, schrieb Robert: >>> Current master is an experimental CAS based implementation- untested and >>> very likely to get completely reworked internally. >> >> Good to know, but that is already a few monce old, or? I remember seeing >> CAS in the code though > It is yes. It is blocke

Re: std.signals regressions - std.signals2

2013-06-17 Thread Robert
> > Current master is an experimental CAS based implementation- untested and > > very likely to get completely reworked internally. > > Good to know, but that is already a few monce old, or? I remember seeing > CAS in the code though It is yes. It is blocked and I got busy with other stuff, so I d

Re: std.signals regressions - std.signals2

2013-06-17 Thread David
>> https://github.com/eskimor/phobos/blob/new_signal/std/signals.d >> >> It is completly unusable, "mixin Signal!() x" is blocked by bug, it >> doesn't compile due to a wrong type (relativly easy fix), then when >> using -unittest it fails to compile, compiler also doesn't give any >> hints what ex

Re: std.signals regressions - std.signals2

2013-06-17 Thread Robert
On Sun, 2013-06-16 at 15:25 +0200, David wrote: > I looked into the "new std.signals" today: Thanks for having a look :-) > > https://github.com/eskimor/phobos/blob/new_signal/std/signals.d > > It is completly unusable, "mixin Signal!() x" is blocked by bug, it > doesn't compile due to a wrong

Re: std.signals regressions - std.signals2

2013-06-16 Thread David
I looked into the "new std.signals" today: https://github.com/eskimor/phobos/blob/new_signal/std/signals.d It is completly unusable, "mixin Signal!() x" is blocked by bug, it doesn't compile due to a wrong type (relativly easy fix), then when using -unittest it fails to compile, compiler also doe