Optional monitors suggestion

[via Digitalmars-d]

On Wednesday, 14 May 2014 at 14:07:50 UTC, Yuriy wrote:
> On Wednesday, 14 May 2014 at 13:53:51 UTC, Damian Day wrote:
>> These would be breaking changes. I see the benefit but...
> Breaking, only if someone used to define __monitor in his 
> class. Which is kinda weird, and according to docs (identifiers 
> starting with __ should are reserved). Or if someone used to 
> access __monitor field of something, which is also kinda weird. 
> Otherwise, no breaking changes here.

The object's layout and size also change, but the layout of 
objects is implementation defined AFAIK, and its size shouldn't 
be hard-coded anyway, so the breakage is minimal.