6 ms·
Range-v3 seems to be solving a different problem. It seems to be introducing support for Pythonesque features like type-checking and list-comprehension. However
by nbingham 9y ago
Range-v3 seems to be solving a different problem. It seems to be introducing support for Pythonesque features like type-checking and list-comprehension. However, the algorithms that are documented still use first/last iterators (http://en.cppreference.com/w/cpp/experimental/ranges/algorithm/sort http://en.cppreference.com/w/cpp/experimental/ranges/algorit...). There seems to be a set of basic range class definitions and there seems to be a View class, but I'm not sure if they interact to provide the same type of generic slice definition that I've developed here.
Perhaps I am missing something though, could you expand a little on the specific part of Range-v3 that you are thinking of?
- beojan 9y agoNo, the primary purpose of range-v3 is to work with ranges (a container, a pair of iterators, or a view) instead of iterators. Lazy and pipeable (i.e. chainable) views are built on top of this. Check the first link rather than the cppreference documentation. By the way, type-checking isn't Pythonesque. Haskellesque perhaps.