http://d.puremagic.com/issues/show_bug.cgi?id=9238
--- Comment #11 from Jonathan M Davis <[email protected]> 2013-01-09 15:11:59 PST --- > There have been ideas based on defining "scope ref", "in ref", or "@attribute > ref". We'd like to avoid such and instead make sure plain "ref" is useful, > safe, and easy to understand. I would argue that it's vital that ref which requires an lvalue and ref which doesn't care whether it's given an lvalue or rvalue be distinguished. You're just begging for bugs otherwise. It should be clear in a function's signature whether it's intending to take an argument by ref and mutate it or whether it's simply trying to avoid unnecessary copying. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
