On 18 January 2015 at 07:20, Walter Bright via Digitalmars-d <[email protected]> wrote: > On 1/17/2015 4:40 AM, Manu via Digitalmars-d wrote: >> >> So when handling ref-related edge cases, do we now have to handle 3 >> cases? not-ref, ref, and return-ref right? >> How do I know if some argument is return-ref? I guess we'll need >> another annoying __traits or something so I can pipe that information >> into my mixins that deal with ref mess... > > > > Or have your mixins generate templates, which will infer 'return'.
*sigh* Don't get me started on auto-ref again. We'll need some sort of traits to detect the return-ref case.
