Re:Living with Microsoft C++ Compiler Bugs and Ambiguities
by progmal1 on Wednesday October 14, 2015 @10:35AM
(#10386827)
I understand that we get in a mess with different compilers not supporting the standard with cross platform code so MSVC should be changed.
But with respect to binding RValues to LValue references, why is the MSVC way not the standard? At first glance the MSVC way appears way more intuitive.
For instance if I have code:
update_X(X());
I would expect to be able to refactor it to this safely:
{
X x;
update_X(x);
}
But with respect to binding RValues to LValue references, why is the MSVC way not the standard? At first glance the MSVC way appears way more intuitive.
For instance if I have code: update_X(X()); I would expect to be able to refactor it to this safely: { X x; update_X(x); }