Re: [boost] boost::thread and move semantics

From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2007-12-17 20:09:15

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 17 December 2007 09:59 am, Anthony Williams wrote:
>
> I have removed detail::thread_move(). Instead, I've added boost::move
> overloads for the movable types in boost.thread: thread, unique_lock<>,
> shared_lock<>, upgrade_lock<>. Since these overloads take specific
> parameter types, they shouldn't cause the problems that the unconstrained
> template caused before.

Have you considered making the mutex types movable?  I'm working on some mutex 
wrapper classes and it would be nice to be able to move construct the wrapper 
from an object of its templated mutex type, instead of assuming the mutex 
type is going to be default constructible.

- -- 
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHZx2/5vihyNWuA4URApOtAJ9eOHs+FasCZtMf3dSIwVS1EIUMCwCeOBOb
rFuxzBcJvDDbxGMRueM588M=
=dr2Z
-----END PGP SIGNATURE-----