"Ion Gaztañaga" <igaztanaga@gmail.com> wrote in message news:45FAD381.1090600@gmail.com...
Gennadiy Rozental wrote:
IOW this library promotes unsafe programming right?
Don't be that hard ;-) Let's say that intrusive containers are interesting for the following purposes:
-> Embedded systems.
It's too generic. So are you saying std::list is not usefull for Embedded systems?
-> High performance algorithms.
How intrusive containers enhance performance?
-> Store non-copyable and non-movable objects.
std::list<T*> does not require copyability either.
-> Low-level memory algorithms, node pools, and similar stuff. -> To build more complex containers, avoiding memory allocations.
What an alternative existing solutions and how your library compare with them?
I agree that Intrusive is not a high-level library comparing it to other Boost libraries, but I really think that it will be very useful to build other Boost libraries. I would say that Intrusive wants to convert some currently unsafe/low-level practices a bit more safer without losing performance.
How safer? How much it adds to handwritten 10 liner intrusive container? Genandiy