« Return to Thread: [thread] Expected behaviour of condition variable wait when the mutex is not locked

Re: [thread] Expected behaviour of condition variable waitwhen the mutex is not locked

by Peter Dimov-5 :: Rate this Message:

Reply to Author | View in Thread

Frank Mori Hess:
> On Thursday 08 May 2008 04:51 am, Anthony Williams wrote:
>> To this end, unique_lock is default-constructible and movable, and
>> supports
>> lock and unlock operations.
>
> Since when is unique_lock default-constructible?  You just mean it has a
> defer_lock_t constructor, right?

It does have a default constructor. Movable types have to have an "empty"
state in which to put the moved-from source, and the default constructor of
a movable type usually creates such an "empty" object. (The proposed promise
doesn't adhere to this "convention" though.)

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

 « Return to Thread: [thread] Expected behaviour of condition variable wait when the mutex is not locked