Re: [boost] [algorithm] adjacent_for_each interest?

Subject: Re: [boost] [algorithm] adjacent_for_each interest?
From: Evgeny Panasyuk (evgeny.panasyuk_at_[hidden])
Date: 2013-02-12 14:13:49

12.02.2013 22:37, Nathan Ridge:
>
>>> By the way, is combine in boost/range/combine.hpp in public api? I don't
>>> see it on website.
>>
>> Nice find! I've been missing a zip_range! A few useful additions would
>> be a corresponding adaptor
>
> Do you mean 'r1 | zipped(r2)' in the place of 'zip(r1, r2)'?
>
> Somehow the asymmetry of that offends me...

I agree.
Especially if consider possible syntax:
1. zip(r1,r2,r3)
2. r1 | zipped(r2) | zipped(r3)

Second is similar to zip(zip(r1,r2),r3) if express in terms of first.

But I don't see quick and straightforward way how to express first in 
terms of second.
Maybe something non-obvious and wild like:
a) r1 | zipped(r2) | merge_zipped(r3)
or
b) r1 | merge_if_zipped(r2) | merge_if_zipped(r3)
?

-- 
Evgeny Panasyuk