id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
7418,Copyable and explicitly movable classes,Daniel James,Ion Gaztañaga,"Making a class movable can have some unfortunate side effects, as far as I know these are all due to implementing implicit moves. So if possible, it's be useful to have a class where the move mechanism only kicks in when boost::move is explicitly used. This could be efficient for cases where the class is explicitly moved (e.g. in a move enable vector), but avoid the potential problems.

I believe that this could be done by defining just the move construct and move assignment, but with no implicit conversions or other special functions. Then the main difficultly is modifying the `has_move_emulation_enabled` trait to support these types. Maybe the class could have a magic member typedef which is detected by sfinae, or maybe you can come up with something better.

Does this sound like a good idea? I haven't tried implementing it, so I might be missing some problem with the idea.",Patches,closed,To Be Determined,move,Boost 1.53.0,Problem,wontfix,,