id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
6610,customizing boost::pool/boost::object_pool via template parameter for ordered/non-ordered usage,rad_d@…,John Maddock,"1.
A documentation conflict between declaration and definition of boost::pool::purge_memory(). The definition documentation is 
{{{
//! pool must be ordered
}}}
, but the declaration documentation does not provide this information.

2.
Version of non-ordered boost::pool::release_memory()

Thereby there is the question - 
are there any differences in implementation or perfomance of ordered/non-ordered versions of this function?

3.
Providing ordered/non-ordered release_memory() and purge_memory() for boost::object_pool

4.
Efficient(non-ordered) construct/destroy of single objects in boost::object_pool(i.e. when boost::object_pool will be used for allocating single objects only, not arrays of objects)

5.
Introduce some template parameter in the boost::object_pool(and in the boost::pool) in order to customize the pool for ordered/non-ordered or both usage.",Feature Requests,new,To Be Determined,pool,Boost 1.48.0,Problem,,,rad_d@…