rvalue references

[deadalnix]

On Tuesday, 23 April 2013 at 08:41:16 UTC, Tove wrote:
> DIP25 imposes a number of code-breaking restrictions even in 
> @system code, if DIP36 was in place, one could consider 
> imposing the DIP25 restrictions only in SafeD.
>
> Furthermore if one day the compiler would be sufficiently smart 
> to infer scope automatically, there still would be an important 
> difference between 'ref' and 'scope ref'.
>

That is the important issue to solve. Many solution can 
jeopardize DIP36, which is why it must be delayed.

Usually conflating issue in adhoc solution ends up in crap that 
must be sorted out later.