Optional monitors suggestion

[Yuriy via Digitalmars-d]

On Thursday, 22 May 2014 at 06:48:17 UTC, Martin Nowak wrote:
> I don't see why we need to introduce a global hashtable 
> (performance impact, not pure). We could warn/deprecate/remove 
> synchronizing on classes without the @monitor attribute.
It's not only about synchronization. Signals use monitors to 
receive finalization callbacks.