id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
1932,move semantics for shared objects (patch),Bryan Green <bryan.d.green@…>,Ion Gaztañaga,"In the interprocess library, move semantics are provided for all the container
types using boost::interprocess::move().

The code for move semantics is (mostly) present in the shared object types and
shared_region, but something is missing for it to actually work for these classes:
the necessary specialization of the 'is_movable' trait, and the correct signature on the
copy constructor and assignment operators.

Attached is a patch that fixes ""movability"" for several types:
file_mapping, shared_memory_object, mapped_region, windows_shared_memory, managed_head_memory, managed_external_buffer.

The problem is a little harder for managed_shared_memory, managed_mapped_file, and managed_windows_shared_memory, because they derive from detail::managed_open_or_create_impl, which currently does not have a default constructor.  I chose not to dig into that at this time.
",Patches,closed,Boost 1.36.0,interprocess,Boost Development Trunk,Problem,fixed,interprocess movable move,