On 11 October 2011 14:41, Andrew Hundt <athundt@gmail.com> wrote:
On Tue, Oct 11, 2011 at 12:41 PM, Eelis van der Weegen <eelis@eelis.net
wrote:
On 2011-10-09 19:59, Andrew Hundt wrote:
Anyone still have additional thoughts or interest in this?
I think this type of container is very useful, and would love to see one in Boost. Should you decide to submit your library for review, I will definitely review it. :)
Eelis
Great, thank you! I'm looking at the submission process page at:
I second that. I've been using boost::array<> with a sentinel value to indicate end, which is both ugly and requires length to be 1 longer than needed. boost::container::static_vector seems like a good addition, maybe it can be reviewed for inclusion in upcoming Boost.Container. FWIW, I think that static_vector should throw std::bad_alloc if it runs out of space, to mimic an out of memory situation for ordinary containers. (Consider an algorithm that needs temporary storage, and user passes a static_vector as tmp storage policy. The algorithm might be designed to handle std::bad_alloc in some way). - Christian