auto ref - again

[Andrei Alexandrescu]

On 1/27/13 9:30 AM, deadalnix wrote:
> On Sunday, 27 January 2013 at 14:09:17 UTC, Andrei Alexandrescu wrote:
>> On 1/27/13 8:05 AM, deadalnix wrote:
>>> It seems here that captures provide you a new copy every time. why not
>>> after all ? What is the problem here ?
>>
>> The property, which is intended to behave as a field as much as
>> possible, in this case continues to look like a field but doesn't act
>> like one. That means that switching transparently between a field and
>> a property (the holy grail of good properties) will silently break code.
>>
>
> OK, I understand. Do you suggest that calling function on rvalue should
> be prevented ?

It's part of the many interactions that must be minded in defining 
properties and binding rvalues to ref.

Andrei