The liabilities of binding rvalues to ref

[Namespace]

> I agree, as long as it doesn't make it insanely difficult (i.e. 
> current situation) to make types that deal with rvalues.
>
> Short answer: no matter what, we have to find a way to be able 
> to write one function that takes by ref, and accepts both 
> rvalues and lvalues.  If ref const is that way, so be it.  If 
> auto ref is that way, so be it.  If it's plain-old ref, I'm 
> fine with that too.
>
> -Steve

We have been looking for a solution since years.  ;)
It will take a very long long time. That is certain.