string foo() { return "hello"; }
int main()
{
//below should be illegal for binding a non-const (lvalue) reference to a rvalue
string& tem = foo();
//below should be the correct one as only const reference can be bind to rvalue(most important const)
const string& constTem = foo();
}
std::string&
from a temporary of type std::string
std::string
to std::string &
A non-const
reference may only be bound to an lvalue&&
, instead in the demo code, I was just using non-const lvalue reference !Can somone help me explain the behavior of VS2010 here? Is it a bug !? Thanks
That is a known issue/feature of the VS compilers. They have always allowed that and there does not seem to be any push into removing that extension.