Just found this:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3153.htm
Showing that implicit move can have adverse effects, especially when blindly
applied to pre-C++11 code.
Could it be why MS doesn't want to implement it?
'=default' should theoretically be fine, since the developer explicitly shows
that they want it -- But I got a reply by email to my OP, saying that
'=default' actually doesn't work on our currently-used MSVC. :-(
On Sunday, May 17, 2015 at 5:38:06 PM UTC+10, gsqu...@mozilla.com wrote:
In Using C++ in Mozilla code (
https://developer.mozilla.org/en-US/docs/Using_CXX_in_Mozilla_code ) there is
this note:
rvalue references: Implicit move method generation cannot be used
First written before Aug 2013, updated by Jcranmer on January 26, 2015
Could we get more details please, e.g.: Why is that (still?) true what to
do about it?
My guess is that some/all compilers don't know how to generate move
constructors assignments, so we need to write explicit ones.
Can we just use '=default' or is that not working either?
Thanks,
Gerald
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
