Re: [boost] GSOC 2013

I think another good project would be a redesign of Boost.Pool, especially now with the stateful allocators of C++11 and Boost.Container. a pool on the stack together with a stateful allocator in an container::vector can replace the often proposed auto_buffer, thread-local pools which only lock a mutex when full, pools with different complexity guarantees (the current Boost.Pool has a often unacceptable linear complexity on delete), containers that "embed" a certain amount of memory which they are likely to use and only allocate when they exceed that size, ...