I would like to draw attention regarding std.signals

[12345swordy via Digitalmars-d]

On Tuesday, 5 September 2017 at 12:09:55 UTC, Bastiaan Veelo 
wrote:
> On Monday, 4 September 2017 at 23:19:31 UTC, 12345swordy wrote:
>> The current bug that I like to focus on is the following:
>> "Not safe for multiple threads operating on the same signals 
>> or slots. "
>>
>> However boost.signals2 is thread safe, so I was wondering what 
>> is currently preventing std.signals from being thread safe? 
>> How hard is it currently?
>
> I don't really know, but there are some alternatives on dub 
> that try to improve on std.signals, for example 
> https://code.dlang.org/packages/phobosx. Not sure thread safety 
> is part of the efforts.
>
> Bastiaan.

The recent updated is from 2015. That's not what I consider to be 
ideal.

Regardless if the bug were to be simply fixed by using mutex then 
it would have it done so already. This implies that it's more 
difficult then it seems which is why I am asking how hard 
currently.