Subject: Re: [boost] [core] [noncopyable] Add nonmoveable?
From: Gavin Lambert (gavinl_at_[hidden])
Date: 2017-04-27 00:21:42
On 27/04/2017 11:23, I wrote:
> If your data members aren't the reason you're constraining movability,
> then why do it at all?
Incidentally, including a mutex in the class members (which is probably
fairly common in multithreaded applications or libraries) also
inherently constrains the class; mutexes (whether std::mutex or from
Boost.Thread) are also neither copyable nor movable, and these traits
pass on to the containing class by default.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk