Marcel
Marcel
Interesting, so the proposal is to access the internal composition of the iterators if they have a natural composition type. For example: zip_view produces (zip_iterator, zip_sentinel) whereas zip_iterator/zip_sentinel is a...
Hi @sergegers, there is no requirement that all ranges are "const-iterable", i.e. that that range offers a const version of the begin/end functions. For example the filters view, see https://eel.is/c++draft/range.filter#view....
I'm sorry, I don't know which popular idioms you are referring to, do you have any links to them? wikipedia? Maybe that helps to understand what you have in mind....
Ah okay, it is expected that some ranges/views can't be const.
Maybe related https://cplusplus.github.io/LWG/issue3480.
@BRevzin Sorry that I ping you, but what are your thoughts on this?
https://github.com/ericniebler/range-v3/blob/fa00307bebb503d58107c6abab3bea4ac4930177/include/range/v3/view/interface.hpp#L508-L535 I guess this code conflicts with yours.
We could change `f2f` in the following ways: * We use the original definition of `f2f` ```c++ #define f2f(function_ptr, ...) ham::function(__VA_ARGS__) ``` and add `f2f_zero` for zero arguments ```c++ #define...
> Boost PP is header only, so shouldn't matter anyways. Yep is also an viable option.
sounds good.