auto ref - again
Dicebot
m.strashun at gmail.com
Sun Jan 27 06:17:24 PST 2013
On Sunday, 27 January 2013 at 14:09:17 UTC, Andrei Alexandrescu
wrote:
> 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.
Some other discussion in property topic made me wonder if
enforcing const on getter non-ref return values makes sense.
More information about the Digitalmars-d
mailing list