std.signals and malloc

David d at dav1d.de
Mon Jan 21 07:47:06 PST 2013


Am 20.01.2013 12:25, schrieb Robert:
> Of course. Just at the moment issue:
> http://d.puremagic.com/issues/show_bug.cgi?id=8441
> 
> is holding it back.

Bugs, as usual.

> It will be probably named std.signals2 or something to maintain
> backwards compatibility, but yeah I definitely want to get it into
> phobos. In fact, I don't even have a use for it in my own projects, I
> just saw the current implementation and thought there must be a better
> way. So the whole point of implementing it, was to get it into phobos.

Good news.


> I strongly encourage you to use my implementation, because real world
> testing before becoming a part of the standard library is always a good
> idea. But keep in mind, that it wasn't formally reviewed yet so your
> code might break, when being included into phobos. (Stuff might get
> renamed for example.) On the other hand fixing this issues should not be
> too much work. So yeah, please try it out, so it will be perfect when
> included. The feature set and set of improvements, should be convincing
> anyway, if not I have done something wrong.

I can't do that, I am using std.signals in a library and I wanna keep it
as small as possible.




More information about the Digitalmars-d mailing list