On Tuesday, 5 September 2017 at 22:04:15 UTC, Jonathan M Davis wrote:
> Personally, the only times that I've done anything that involved something like this have been for GUI programming, and that usually involves mechanisms connected to the GUI toolkit. If I were looking to do anything that involved sending messages across threads, I'd be using std.concurrency, not std.signals, and if I weren't specifically dealing with multiple threads, I wouldn't see much point in the whole signals and slots thing.

I'd say signals are not for multithreading, especially if they are for GUI.

On Wednesday, 6 September 2017 at 09:50:22 UTC, Kagamin wrote:
> On Tuesday, 5 September 2017 at 22:04:15 UTC, Jonathan M Davis wrote:
>> Personally, the only times that I've done anything that involved something like this have been for GUI programming, and that usually involves mechanisms connected to the GUI toolkit. If I were looking to do anything that involved sending messages across threads, I'd be using std.concurrency, not std.signals, and if I weren't specifically dealing with multiple threads, I wouldn't see much point in the whole signals and slots thing.
>
> I'd say signals are not for multithreading, especially if they are for GUI.

Why do you think that boost library signals2 exist then?