Doesn't std.signal completely miss the point?

[Nick Treleaven]

On 04/09/2011 22:27, Andrej Mitrovic wrote:
> From what I can tell std.signal is designed around the idea that an
> entire class acts as a signal emitter, without the ability to write
> multiple signals within one class and making arbitrary connections
> between signals and slots.

I for one was surprised when I looked at it a while ago and found it 
doesn't seem to support multiple signals per class. I'm no expert but 
I'm used to GTK+ named signals and expected something comparable.