23 Jul
2011
23 Jul
'11
12:21 p.m.
On Fri, Jul 22, 2011 at 6:16 PM, Mathias Gaunard <mathias.gaunard@ens-lyon.org> wrote:
That explains the strange problems I had when I tried using sub_range. iterator_range does not have those problems.
But it seems to be a feature, it you look at the doc of sub_range it says, when comparing sub_range to iterator_range, "Moreover, the sub_range class can propagate constness since it knows what a corresponding const_iterator is."
This is, in my opinion, a mistake. const sub_range<T> should *not* behave like sub_range<const T>.
Why (not)? What's the problem with it? Olaf