Range library for C++11/14/17. This code is the basis of a formal proposal to add range support to the C++ standard library.
Why does C++ need another range library? Simply put, the existing solutions haven't kept up with the rapid evolution of C++. Range v3 is a library for the future C++. Not only does it work well with today's C++ -- move semantics, lambdas, automatically deduced types and all -- it also anticipates tomorrow's C++ with Concepts.
Range v3 forms the basis of a proposal to add range support to the standard library (N4128: Ranges for the Standard Library). It also will be the reference implementation for an upcoming Technical Specification. These are the first steps toward turning ranges into an international standard.
Check out the (woefully incomplete) documentation here.
Other resources (mind the dates, the library probably has changed since then):
-
Usage:
- Talk: CppCon 2015: Eric Niebler "Ranges for the Standard Library", 2015.
- A slice of Python in C++, 07.12.2014.
- Actions (back then called Container Algorithms), 23.11.2014.
- Range comprehensions, 27.04.2014.
- Input iterators vs input ranges, 07.11.2013.
-
Design / Implementation:
- Rationale behind range-v3: N4128: Ranges for the standard library Revision 1, 2014.
- Ranges TS: N4560: C++ Extensions for Ranges, 2015.
- Implementation of customization points in range-v3:
- Proxy iterators in range-v3:
- Metaprogramming utilities:
- See the meta documentation, the library has changed significantly since the 2014 blog post.
- Concept emulation layer: Concept checking in C++11, 2013.
- C++Now 2014: Eric Niebler "C++11 Library Design", 2014.
Most of the source code in this project are mine, and those are under the Boost Software License. Parts are taken from Alex Stepanov's Elements of Programming, Howard Hinnant's libc++, and from the SGI STL. Please see the attached LICENSE file and the CREDITS file for the licensing and acknowledgments.
The code is known to work on the following compilers:
- clang 3.6.2 (or later)
- GCC 4.9.1 (or later) (C++14 support requires GCC 5.2; C++14 "extended constexpr" support is poor before 6.1.)
- Clang/LLVM 6 (or later) on Windows (older versions may work - we haven't tested.)
[ Note: We've "retired" support for Clang/C2 with the VS2015 toolset (i.e., the v140_clang_c2
toolset) which Microsoft no longer supports for C++ use. We no longer have CI runs, but haven't gone out of our way to break anything, so it will likely continue to work. ]
Development Status: This code is fairly stable, well-tested, and suitable for casual use, although currently lacking documentation. No promise is made about support or long-term stability. This code will evolve without regard to backwards compatibility.
Build status
-
0.3.6 May 15, 2018
- NEW:
view::exclusive_scan
(thanks to GitHub user @mitsutaka-takeda). - All views get non-
const
overloads of.empty()
and.size()
(see ericniebler/stl2#793). - Upgrade Conan support for conan 1.0.
subspan
interface tweaks.- Fix bug in
view::split
(see this stackoverflow question). - Fix bug in
view::stride
(see ericniebler/stl2#805). - Fix
const
-correctness problem inview::chunk
(see this stackoverflow question). - Replace uses of
ranges::result_of
withranges::invoke_result
. - Fix potential buffer overrun of
view::drop
over RandomAccessRanges. - Lots of
view::cartesian_product
fixes (see ericniebler/stl2#820, ericniebler/stl2#823). - Work around gcc-8 regression regarding
volatile
std::initializer_list
s (see ericniebler/stl2#826). - Fix
const
-correctness problem ofview::take
.
- NEW:
-
0.3.5 February 17, 2018
- Rvalues may satisfy
Writable
(see ericniebler/stl2#387). view_interface
gets a bounds-checkingat
method.chunk_view
works on Input ranges.- Fix bug in
group_by_view
. - Improved concept checks for
partial_sum
numeric algorithm. - Define
ContiguousIterator
concept andcontiguous_iterator_tag
iterator category tag. - Sundry
span
fixes. action::insert
avoids interfering withvector
's exponentional growth strategy.- Add an experimental
shared
view for views that need container-like scratch space to do their work. - Faster, simpler
reverse_view
. - Rework
ranges::reference_wrapper
to avoid LWG#2993. - Reworked
any_view
, the type-erased view wrapper. equal
algorithm isconstexpr
in C++14.stride_view
no longer needs anatomic
data member.const
-correctdrop_view
.adjacent_filter_view
supports bidirectional iteration.- Massive
view_adaptor
cleanup to remove the need for amutable
data member holding the adapted view. - Fix
counting_iterator
post-increment bug. tail_view
of an empty range is an empty range, not undefined behavior.- Various portability fixes for gcc and clang trunk.
- Rvalues may satisfy
-
0.3.0 June 30, 2017
- Input views may now be move-only (from @CaseyCarter)
- Input
any_view
s are now much more efficient (from @CaseyCarter) - Better support for systems lacking a working
<thread>
header (from @CaseyCarter)
-
0.2.6 June 21, 2017
- Experimental coroutines with
ranges::experimental::generator
(from @CaseyCarter) ranges::optional
now behaves likestd::optional
(from @CaseyCarter)- Extensive bug fixes with Input ranges (from @CaseyCarter)
- Experimental coroutines with
-
0.2.5 May 16, 2017
view::chunk
works on Input ranges (from @CaseyCarter)for_each_n
algorithm (from @khlebnikov)- Portability fixes for MinGW, clang-3.6 and -3.7, and gcc-7; and cmake 3.0
-
0.2.4 April 12, 2017 Fix the following bug:
action::stable_sort
ofvector
broken on Clang 3.8.1 since ~last Xmas (ericniebler#632).
-
0.2.3 April 4, 2017 Fix the following bug:
- iterators that return move-only types by value do not satisfy Readable (ericniebler/stl2#399).
-
0.2.2 March 30, 2017 New in this release:
view::linear_distribute(from,to,n)
- A view ofn
elements betweenfrom
andto
, distributed evenly.view::indices(n)
- A view of the indices[0,1,2...n-1]
.view::closed_indices(n)
- A view of the indices[0,1,2...n]
.
This release deprecates
view::ints(n)
as confusing to new users. -
0.2.1 March 22, 2017 New in this release:
view::cartesian_product
action::reverse
-
0.2.0 March 13, 2017 Bring many interfaces into sync with the Ranges TS.
-
Many interfaces are simply renamed. The following table shows the old names and the new. (All names are in the
ranges::v3
namespace.)Old Name New Name indirect_swap
iter_swap
indirect_move
iter_move
iterator_value_t
value_type_t
iterator_reference_t
reference_t
iterator_difference_t
difference_type_t
iterator_size_t
size_type_t
iterator_rvalue_reference_t
rvalue_reference_t
iterator_common_reference_t
iter_common_reference_t
range_value_t
range_value_type_t
range_difference_t
range_difference_type_t
range_size_t
range_size_type_t
range_iterator_t
iterator_t
range_sentinel_t
sentinel_t
-
common_iterator
now requires that its two types (Iterator
andSentinel
) are different. Usecommon_iterator_t<I, S>
to get the old behavior (i.e., if the two types are the same, it is an alias forI
; otherwise, it iscommon_iterator<I, S>
). -
The following iterator adaptors now work with iterators that return proxies from their postfix increment operator (i.e.,
operator++(int)
):common_iterator
counted_iterator
-
The following customization points are now implemented per the Ranges TS spec and will no longer find the associated unconstrained overload in namespace
std::
:ranges::begin
ranges::end
ranges::size
ranges::swap
ranges::iter_swap
(In practice, this has very little effect but it may effect overloading in rare situations.)
-
ranges::is_swappable
now only takes one template parameter. The newranges::is_swappable_with<T, U>
tests whetherT
andU
are swappable.ranges::is_swappable<T>
is equivalent toranges::is_swappable_with<T &, T &>
. -
The following object concepts have changed to conform with the Ranges TS specification, and approved changes (see P0547):
Destructible
Constructible
DefaultConstructible
MoveConstructible
MoveConstructible
Movable
Assignable
-
The
View
concept is no longer satisfied by reference types. -
The syntax for defining a concept has changed slightly. See utility/iterator_concepts.hpp for examples.
-
-
0.1.1 Small tweak to
Writable
concept to fix #537. -
0.1.0 March 8, 2017, Begin semantic versioning
I do this work because I love it and because I love C++ and want it to be as excellent as I know it can be. If you like my work and are looking for a way to say thank you, you can leave a supportive comment on my blog. Or you could leave me some kudos on my Open Hub range-v3 contribution page. Just click the Give Kudos button here.