Subject: Re: [Boost-bugs] [Boost C++ Libraries] #6536: All container constructors should have a variant taking an allocator as a final parameter
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-02-18 01:29:20
#6536: All container constructors should have a variant taking an allocator as a
final parameter
-------------------------------------------------+--------------------------
Reporter: Erik Jensen <Erik.Jensen@â¦> | Owner: igaztanaga
Type: Bugs | Status: new
Milestone: To Be Determined | Component: container
Version: Boost 1.49.0 | Severity: Problem
Resolution: | Keywords:
-------------------------------------------------+--------------------------
Comment (by Erik Jensen <Erik.Jensen@â¦>):
Replying to [comment:1 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()); }
}}}
or
{{{
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.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/6536#comment:2> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:09 UTC