I am aware of tuples are, will, and should never be considered as a view #1247 .
I am also most thankful of the utilities provided in <utility/tuple_algorithm.hpp>, namely the tuple transform / apply / fold / for_each.
To my understanding, since pipe operator support comes from view_adaptor, the utilities don't come with fluent syntax, i.e.
ranges::tuple_for_each(std::tuple{1, 2, "3"}, std::identity {}); // OK
std::tuple{1, 2, "3"} | ranges::tuple_for_each(std::identity {}); // ERROR -- no pipe!
I am curious if it is possible for one to implement a tuple_adaptor concept,
or what's the fundamental gap that led us to the point where the library ( and the std ) only support view_adaptor instead of exposing a more general T_adaptor concept
Hi,
I am aware of tuples are, will, and should never be considered as a view #1247 .
I am also most thankful of the utilities provided in
<utility/tuple_algorithm.hpp>, namely the tuple transform / apply / fold / for_each. To my understanding, since pipe operator support comes fromview_adaptor, the utilities don't come with fluent syntax, i.e.I am curious if it is possible for one to implement a
tuple_adaptorconcept, or what's the fundamental gap that led us to the point where the library ( and the std ) only supportview_adaptorinstead of exposing a more generalT_adaptorconceptThanks in advance