On Thursday, 24 January 2013 at 14:19:34 UTC, Jacob Carlborg
wrote:
On 2013-01-24 15:04, deadalnix wrote:
No, which would eliminate the difference behavior between
function as
variables and function defined in source code. This is a big
step
forward for functional style.
Then what do you mean by:
&a.foo; // deprecated NOOP for compatibility.
a.foo is the same as &a.foo . The reason is that &a.foo is used
in a lot of code today as it is the only way to perform such
action.
As a.foo is not an rvalue, it does not conflict. To achieve the
ideally consistent behavior it should be disabled at some point.
