std.signals regressions - std.signals2
Robert
jfanatiker at gmx.at
Mon Jun 17 12:38:54 PDT 2013
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 type (relativly easy fix), then when
> using -unittest it fails to compile, compiler also doesn't give any
> hints what exactly fails.
Current master is an experimental CAS based implementation- untested and
very likely to get completely reworked internally.
> Removing these unittests makes it at least compile, but the other
> unittests fail (assert). Removing also these unittests (hoping it still
> works), nope it doesn't signals aren't triggered at all.
>
> Are there any plans on improving this situation with std.signals or the
> new implementation, currently both are getting less useable every day...
> (e.g. signal.disconnect(&my_handler) disconnects all, yay what a joy)
There are plans absolutely, to be concrete: I plan to make it ready in
July. There is one blocker currently:
http://d.puremagic.com/issues/show_bug.cgi?id=8441
but there is already an aging pull request which fixes it:
https://github.com/D-Programming-Language/dmd/pull/1660 (4 months old
already)
I hope it will be merged soon, then there is hopefully nothing that
hinders my plans. The very least it should become ready during summer.
>
>
> I am hijacking this thread in hope someone will read that ;)
> Hopefully also someone of the "new std.signals" developers.
I almost missed it ;-)
Sorry about your bad experiences with the current version.
Best regards,
Robert
More information about the Digitalmars-d
mailing list