compile-time checked access

[Tobias Loew]

Since code like

boost::array<int,2> test; test[2] = 1; test[-1] = 1;

compiles correctly on some compilers (even without warnings). I suggest adding compile checked functions for static access to arrays like:

template<size_type i> reference at() {

BOOST_STATIC_ASSERT( (i < N) ); return elems[i];

}

template<size_type i> const_reference at() const {

BOOST_STATIC_ASSERT( (i < N) ); return elems[i];

}

then code like:

boost::array<int,2> test; test.at<2> = 1; test.at<-1> = 1;

would result in the expected errors.

[Marshall Clow]

Yes, it would - but would people actually use it?

Do people use:

std::array<int, 2> arr;
std::get<2>(arr) = -1;

in C++11 - or do they just write arr[2] = -1; ?

boost::array (and std::array, and std::vector) all have runtime checking through the member function at.

boost::array<int, 2> arr;
arr.at(2) = -1;    // will throw an exception

[Marshall Clow]

In [82083], I added support for std::get<> to Boost.Array, so you can write

boost::array<int, 2> arr;
std::get<2>(arr) = -1;

and get a compile-time error.

Right now, it's only turned on for C++11, but I might be able to make it work for C++03 systems.

[anonymous]

The stl-version of VS 2008 has the same code for "get" and std::tr1::array<T,N> and it compiles fine with C++03, so it works at least for that compiler.

[Tobias Loew]

I made the last comment but forgot to login, sorry

[Marshall Clow]

I also added overloads of boost::get for use on C++03

[Marshall Clow]

Also, in [82834], I marked a bunch of methods of Boost.Array as "constexpr".