range-v3

range-v3 is a great library allowing you to bridge the gap: https://github.com/ericniebler/range-v3

The upcoming ranges library will provide exactly this! It uses | for composing operations. See e.g. here: https://github.com/ericniebler/range-v3/tree/master/example

> C++ is inherently OOP in 1985 maybe. It was already pretty much not OOP in 1999 with libraries such as boost.graph, and is as far from "Java/C#" oop that you can imagine in 2018, where you can easily build lazy functional pipelines (https://github.com/ericniebler/range-v3), pattern-match (https://github.com/mpark/patterns), and where generic programming is the dominant paradigm.

It’s worth noting that C++ has been adopting python’s functional attributes, from range-based loops, <algorithm> , duck-typing, and fold expressions, to libraries supporting Python’s style more directly. Range-v3 [0] and cppitertools [1] stand out to me. The former is in a current proposal for inclusion in the C++20 standard. [0] https://github.com/ericniebler/range-v3 [1] https://github.com/ryanhaining/cppitertools

Range-v3 (https://github.com/ericniebler/range-v3) exists solving the same problem, and there's a standardization proposal (http://en.cppreference.com/w/cpp/experimental/ranges).

Two previous Reddit threads on this topic: https://www.reddit.com/r/cpp/comments/489f9l/open_source_pro... https://www.reddit.com/r/cpp/comments/5sxrun/what_are_some_e... My list: SeaStar and ScyllaDB https://github.com/scylladb/seastar https://github.com/scylladb/scylla Cap'n Proto https://github.com/sandstorm-io/capnproto LLVM range-v3 https://github.com/ericniebler/range-v3 Facebook folly https://github.com/facebook/folly easylambda https://github.com/haptork/easylambda thrust https://github.com/thrust/thrust xtensor https://xtensor.readthedocs.io/en/latest/numpy.html

I would name Eric Nieblers range-v3 library : https://github.com/ericniebler/range-v3 - amazing stuff.

Whats holding you back then? Eric Nieblers Range-v3 library is available: https://github.com/ericniebler/range-v3/ Its not going to be (much) better in the standard... Except that it would use real concepts then...

We've been seeing similar attempts recently, all attempting to fill a long overdue gap: the composability of algorithms in the standard library. At this point, there exists a TS [1] for ranges [2] along with an implementation [3]. It will be a thin layer on top of the iterator-based standard library, sometimes dubbed "STL2." On the one hand, it's great to new attempts to compose algorithms mushrooming, but on the other hand it would be great to see more aligned efforts to collaboratively push forward the TS and its implementation. [1] A technical specification (TS) can be thought of as a self-contained mini standard that vendors can implement, but do not have to in order to be "standard-compliant". A is a promising candidate for future inclusion into the standard, however. [2] https://ericniebler.github.io/std/wg21/D4128.html [3] https://

Do you mean Eric Niebler's ranges[1] library? [1]https://github.com/ericniebler/range-v3

Similar to this effort, Eric Niebler's range library [1,2] aims at improving algorithm composability. The range library offers both an eager and lazy API. This is the lazy version (views): int sum = accumulate(view::ints(1) | view::transform([](int i) {return i * i;}) | view::take(10), 0); And this the eager (via actions): extern std::vector<int> read_data(); std::vector<int> vi = read_data(); action::unique; vi = std::move(vi) | action::sort | action::unique; Eric puts in a lot of effort to make this library part of the C++ standard (see proposal N4128 [3]). [1] https://github.com/ericniebler/range-v3 [2] User Manual with code examples: https://ericniebler.github.io/range-v3/index.html [3] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n412...

Ranges are coming: https://github.com/ericniebler/range-v3/blob/master/doc/D412...

> The issue with extending operators in this fashion is that you're violating the principle of least surprise. It is really common for the `|` operator to be used for piping functions together. There are several libraries that support it: [Boost.Range](http://www.boost.org/doc/libs/1_56_0/libs/range/doc/html/ind...), [PStade Oven](http://p-stade.sourceforge.net/oven/doc/html/index.html), [Linq](http://pfultz2.github.io/Linq/), and [Streams](http://jscheiny.github.io/Streams/). Plus, its even being proposed as part of the ranges library in future C++: https://github.com/ericniebler/range-v3/blob/master/doc/D412... So just as the bit shift operators in C++ also have the meaning of streaming in and out, the bitwise or also has the meaning of pipe, so this is should not at all be a suprise.