Re: [container] static_string ?

From: Hans Dembinski (hans.dembinski_at_[hidden])
Date: 2019-09-10 09:08:30

> On 9. Sep 2019, at 23:03, Ion Gaztañaga via Boost <boost_at_[hidden]> wrote:
> 
> On 09/09/2019 20:23, Zach Laine via Boost wrote:
>> On Mon, Sep 9, 2019 at 9:59 AM Vinnie Falco via Boost <boost_at_[hidden]>
>> wrote:
>>> Beast has static_string which someone has asked to be move, is there
>>> any interest in moving this to Boost.Container?
>>> 
>>> See:
>>> 
>>> <https://github.com/boostorg/beast/issues/1691>
>>> 
>>> <
>>> https://github.com/boostorg/beast/blob/b7230f12f16fe7a9f7a1ece5be1f607c8552448a/include/boost/beast/core/static_string.hpp
>>>> 
>>> 
>> This is of course a question for Ion, but I would like to see this made
>> more widely available.
> 
> Hi,
> 
> Sorry for the delay. I think it's a good idea, it seems a really useful container. To ease the maintenance, I think we should merge container::string and container::static_string implementations to reuse as much as code as we can.

This was probably discussed here before, but could someone remind me why static_string and static_vector need to exist as separate containers at all? Why don't we use a boost::vector and boost::string with a special allocator that offers a fixed-sized memory pool allocated from the stack?