19 Nov
2016
19 Nov
'16
9:11 a.m.
El 18/11/2016 a las 12:02, Thorsten Ottosen escribió:
On 16-11-2016 18:39, Joaquin M López Muñoz wrote:
I'm in principle somewhat reluctant to add lib-specific mechanisms for generic operations such as copying (although the friend class boost::poly_collection::access thing is an opt-in feature not really needed for publicly copyable classes); that said, my wish is to flexible with whatever reviewers mostly agree on.
Yes, please consider it. Most OO-hierarchies start off with prohibiting copying by inheriting from boost::noncopyable or something similar. It would be a shame if such hierarchies would now be /forced/ to have public copy/move operations.
Point taken. Joaquín M Lopez Muñoz