On Mon, 18 Nov 2013, Trevor Saunders wrote:

This patch adds a class auto_vec which releases its internal storage in its destructor, but unlike stack_vec it has no built in storage so its reasonable to use it in objects on the heap. It then replaces a bunch of vectors on the stack with stack_vec if the initial creation size was a compile time constant or auto_vec otherwise.

Why not use stack_vec<T, 0>? You could partially specialize it if there
is waste, and you could make the 0 implicit.

--
Marc Glisse

Reply via email to