On Saturday, 30 March 2013 at 09:17:17 UTC, Namespace wrote:
And to pull the reverse: Why should '@val ref' be more
intuitive than ref&? Or why should be '@ref' more intuitive?
What I mean by that:
Both the Property as well as the hybrid path have their
weaknesses and are not necessarily immediately obvious. But we
should choose one of them and focus on this so that somebody
can make a pull request for it.
Because & in C++ means "by ref".
D has "ref" for that.
So ref& doesn't make sense. One might think it as a double
reference(?)
