Adam Wulkiewicz wrote:
One use case is "inserting run-time number of elements to the container which should store compile-time number of elements finished by throwing an exception". A workaround of a problem which is "exiting from some routine's internals at some point of execution in possibly unknown place". This will work with some routines and don't with others which treat exceptions differently. And you're saying that only one specific conainer is intended for this task because other won't throw an exception in this case.
No. What I'm saying is that a throwing push_back (A1) is a better fit when the potential number of elements is not bounded by a compile time constant (B1). (Conversely, a "preconditioned" push_back (A2) is a better fit when the potential number of elements is bounded by a compile time constant (B2).)