There is a study group on ranges in the C++ committee:
but I have not followed the history of this study group and I am not sure of what kind of delivery is expected for C++1z (furthermore I do not use boost.range so I do not have a clear view of existing practices). Will we have:
ranges as a pair of first/last iterators?
union and other set operations on ranges(for example
[v.begin()+5, v.begin()+7[ U [v.begin()+10, v.begin()+15[ U [v.begin()+21, v.begin()+42[
), namely: union, intersection, disjoint union, complement?iterator filters (in order to execute a for_each where a condition is satisfied)?
other things?
Eric Niebler initiated discussion of his
Iterable
work (four-part blog posting: Part 1, Part 2, Part 3, Part 4) on the SG9 mailing list on Feb 27. There's been quite a bit of back and forth since then, especially considering that the list had been dead for about a year.As near as I can tell as an outsider, the SG is in the "arguing about what they're trying to do" phase which is quite far from the "developing wording for a Standard/Technical Specification" phase. This is, however, a substantial move forward from the "dormant" phase. The meeting minutes from the last few committee meetings are illuminating:
2013-05-03 (Bristol):
2013-10-16 (Chicago):
2014-03-03 (Issaquah):
It hasn't exactly been going like gangbusters, and there is no set deliverable goal AFAIK.