On 15/01/2012 14:12, Peter Alexander wrote: <snip>
I agree with requiring ref at the call site in principle, although it would be too much of a breaking change to introduce now. Perhaps allow it, and issue a warning if not used?
Maybe phase it in in this sequence: 1. Allow ref/out at call site. 2. Add a warning for if ref/out at call site is omitted. 3. Deprecate omitting ref/out at call site. 4. Require ref/out at call site. 5. Allow overloading of functions based on parameter storage class, as much as makes sense. Stewart.
