id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
7321,freelist_stack::allocate and freelist_stack::deallocate should not be private,Hartmut Kaiser,timblechmann,"Currently, the allocate/deallocate functions et.al. in lockfree::detail::freelist_stack are private. This inhibits reusing this class for implementing other lock-free datastructures as it's not possible to allocate anything which has not a constructor taking 0, 1, or 2 arguments (those are supported explicitly by exposing overloads for freelist_stack::construct).

Would it be possible to make the mentioned functions 'protected' instead?

",Bugs,closed,To Be Determined,lockfree,Boost 1.52.0,Problem,fixed,,