Standard way of getting a non-specialized std::vector<bool> container

Question

Is there a standard way (or at least semi-standard, implemented in all popular compilers) to get a non-specialized, non-optimized, contiguous std::vector<bool> container?

I have some generic code dealing with std::vectors which assumes they are all such standard, contiguous containers. My current workaround is to use a std::vector<int> which just stores 0's and 1's, which is what I want content-wise, but it would be nicer to have the correct vector type.

Answer 1

As workaround you might use other type, char comes in mind. Else you can write a wrapper around bool, something like:

struct my_bool
{
    operator bool() const { return b; }
    operator bool&() { return b; }

    bool b;
};

Answer 2

Generally, use of std::vector<bool> specialization is not consider a good practice, with exceptions of-course. Mainly, because its interface is different with that of the primary std::vector<T> and this causes a lot of confusion.

This irregularity, is mentioned in several publications that are loose in the web. A recent one and IMHO a good read is written by Howard Hinnant namely On vector<bool>.

In fact sometime ago there was a proposal to remove it from from the standard N1185, but it was rejected for backward compatibility issues.

Most proposed semi-standard alternative is the use of std::vector<unsigned char> or std::vector<char>.