rvalues -> ref (yup... again!)

[Nick Sabalausky (Abscissa)]

On 03/23/2018 09:06 PM, Jonathan M Davis wrote:
> 
> My biggest concern in all of this is that I don't want to see ref start
> accepting rvalues as has been occasionally discussed. It needs to be clear
> when a function is accept an argument by ref because it's going to mutate
> the object and when it's accepting by ref because it wants to avoid a copy.
> 

That ship sailed ages ago: It's already unclear. If we want to fix that, 
we can fix it, but blocking rvalue ref does nothing for that cause.