Possible @property compromise

[Zach the Mystic]

On Wednesday, 30 January 2013 at 01:20:39 UTC, Zach the Mystic 
wrote:
> On Wednesday, 30 January 2013 at 01:09:12 UTC, H. S. Teoh wrote:
>> There's also the consideration of what happens if you take the 
>> address
>> of the 'pseudo' variable: the inner struct would then be 
>> effectively
>> dissociated from the parent struct, and you'll need that 
>> hidden context
>> pointer (along with its gotchas) in order to have things still 
>> work as
>> before.
>
> Compiler detects a struct which holds no data of its own and 
> disallows taking its address.

Actually, you're right. I see no overloading of the address 
operator in the documentation. I doubt it's an insurmountable 
problem, though. opAddress?