Ion Gaztañaga — Sat, 11 Feb 2012 12:03:29 GMT

Sorry, the scoped allocator model is not implemented yet, let's see if I can find time to bring it in Boost 1.50. Thanks for the ticket.

Sat, 18 Feb 2012 01:29:19 GMT

Replying to igaztanaga:

Sorry, the scoped allocator model is not implemented yet, let's see if I can find time to bring it in Boost 1.50. Thanks for the ticket.

I know the model itself is not supported, but the new C++11 constructors are useful for more than just that, and it seems like implementation should be pretty simple. For example,

basic_string(const basic_string& s, const allocator_type& a)
   :  base_t(a)
{ this->priv_range_initialize(s.begin(), s.end()); }

vector(const vector &x, const allocator_type &a)
: base_t(a)
{
   this->assign( container_detail::to_raw_pointer(x.members_.m_start)
               , container_detail::to_raw_pointer(x.members_.m_start + x.members_.m_size));
}

Of course, there are probably more complications that I am overlooking.

Thanks again for you consideration.

status changed; resolution set

Ion Gaztañaga — Fri, 24 Aug 2012 21:38:55 GMT

status new → closed
resolution → fixed

Fixed in Boost 1.50

Boost C++ Libraries: Ticket #6536: All container constructors should have a variant taking an allocator as a final parameter

status changed; resolution set