Hi, ----- Original Message ----- From: "Ion Gaztañaga" <igaztanaga@gmail.com> To: <boost@lists.boost.org> Sent: Tuesday, February 17, 2009 11:00 PM Subject: [boost] [move] Library uploaded to sandbox
Hi to all,
<snip>
The library needs specially modified Interprocess containers (and Intrusive because of dependences), which I've also uploaded to sandbox. The examples show how movable only values can be inserted into containers.
I think this needs a clarification. The MoveEmulation library do not depends neither on Boost.Interprocess not on Boost.Intrusive. Isnt't it? <snip>
I've invested some precious time in the library and testing different approaches to see if it plays well with containers but I would like to hear some comments on whether the direction is acceptable and if I should spend more time on it. If someone else with more time wants to continue the library, please do it! ;-)
I appreciate the good work you have done. Thanks Ion.
I've personally added to the library all that I've seen useful for move-aware containers, so it might lack some features (move aware algorithms, for example).
Now that you have already tested with your InterProcess and Intrusive containers I'll adapt my own libraries to use it and see how it works.
Anyway, my opinion is that we need some move library, better now than later even if it's too basic, so that we can unify all redundant move emulation that we already have in boost libraries. I hope this is a step in the right direction.
I completly agree. What about requesting a formal review? Thanks again, Vicente