On 9/16/14, 11:26 AM, monarch_dodra wrote:
Arguably, the issue is not const ref binding to an rvalue itself, but rather taking (and *holding*) the address of a parameter that is passed by const ref
It doesn't do that. It holds pointer/length to the slice, which is different and distinct from the pointer to the string. -- Andrei
