I removed the __monitor field from Object, but...
Error: `TypeInfo_Struct`: mismatch between compiler (136 bytes) and object.d or object.di (128 bytes) found
class TypeInfo_Struct : TypeInfo
^
So... apparently the compiler has some sort of internal affinity for the typeinfo of the thing being compiled? I'd rather like to think the compiler shouldn't be coupled to the output in that way.
But there's a further problem; if I add __monitor back to my Object to try and suppress this error, DMD (master) stops complaining, but LDC does complain, because it's still internal to that compiler.
Can anyone think if a clever compile time condition I can use to determine if I should include __monitor in Object or not? I need some kind of way to determine if the frontend expects it to be declared in object.d or if it's still internally defined.
I removed the
__monitorfield fromObject, but...So... apparently the compiler has some sort of internal affinity for the typeinfo of the thing being compiled? I'd rather like to think the compiler shouldn't be coupled to the output in that way.
But there's a further problem; if I add
__monitorback to myObjectto try and suppress this error, DMD (master) stops complaining, but LDC does complain, because it's still internal to that compiler.Can anyone think if a clever compile time condition I can use to determine if I should include
__monitorinObjector not? I need some kind of way to determine if the frontend expects it to be declared inobject.dor if it's still internally defined.