http://llvm.org/bugs/show_bug.cgi?id=19123
David Blaikie <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |[email protected] Resolution|--- |INVALID --- Comment #1 from David Blaikie <[email protected]> --- This deprecation is enshrined in the C++11 standard: " If the class definition declares a move constructor or move assignment operator, the implicitly declared copy assignment operator is defined as deleted; otherwise, it is defined as defaulted (8.4). The latter case is deprecated if the class has a user-declared copy constructor or a user-declared destructor." So "= default" doesn't help here. Note that this is even more problematic in the face of move operations - defining an implicit move op as explicitly defaulted will disable (define as deleted, as seen in the above wording) copy operations. Providing implicit ops explicitly with = default isn't a noop and should be avoided. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
