[Boost-users] [Containers Library Review] The review of the Containers library by Ion Gaztanaga starts today

Subject: [Boost-users] [Containers Library Review] The review of the Containers library by Ion Gaztanaga starts today
From: John Maddock (boost.regex_at_[hidden])
Date: 2011-08-03 06:53:45

The review of the containers library by Ion Gaztanaga starts today, to 
summarize the library:

"Boost.Container library implements several well-known containers, including 
STL containers. The aim of the library is to offers advanced features not 
present in standard containers or to offer the latest standard draft 
features for compilers that comply with C++03.

In short, what does Boost.Container offer?

    * Move semantics are implemented, including move emulation for pre-C++0x 
compilers.
    * New advanced features (e.g. placement insertion, recursive containers) 
are present.
    * Containers support stateful allocators and are compatible with 
Boost.Interprocess (they can be safely placed in shared memory).
    *

      The library offers new useful containers:
          o flat_map, flat_set, flat_multiset and flat_multiset: drop-in 
replacements for standard associative containers but more memory friendly 
and with faster searches.
          o stable_vector: a std::list and std::vector hybrid with 
random-access iterators that offers iterator stability in insertions and 
erasures.
          o slist: the classic pre-standard singly linked list container."

Documentation from the library may be viewed online here: 
file:///M:/data/boost/sandbox/move/libs/container/doc/html/index.html

The source may be accessed from the "move" directory of the sandbox SVN or 
downloaded from http://www.drivehq.com/web/igaztanaga/boost_container.zip. 
Note that this download contains a copy of the accepted, but not yet 
release, Boost.Move library - extract the zip over a copy of Boost-1.47 to 
get a full working copy.

Review comments might like to answer the following questions:

    *  What is your evaluation of the design?
    * What is your evaluation of the implementation?
    * What is your evaluation of the documentation?
    * What is your evaluation of the potential usefulness of the library?
    * Did you try to use the library? With what compiler? Did you have any 
problems?
    * How much effort did you put into your evaluation? A glance? A quick 
reading? In-depth study?
    * Are you knowledgeable about the problem domain?

And finally, every review should answer this question:

    * Do you think the library should be accepted as a Boost library? Be 
sure to say this explicitly so that your other comments don't obscure your 
overall opinion.

Regards, John Maddock.