The liabilities of binding rvalues to ref

[deadalnix]

On Sunday, 5 May 2013 at 05:49:42 UTC, Andrei Alexandrescu wrote:
> There may be other important patterns to address at the core, 
> please chime in. I consider (1) above easy to tackle, which 
> leaves us with at least (2). My opinion is that any proposal 
> for binding rvalues to ref must offer a compelling story about 
> these patterns.
>

Yes ! With optional parenthesis, it is super unclear if we access 
an lvalue or an rvalue and update its content or not.

A good example of that is the captures property from std.regex. 
The property is an revalue, and would look like a filed that 
reset itself all the time if bound to an lvalue.