Re: [Boost-users] [Range] Sliced... less than it could be.

Subject: Re: [Boost-users] [Range] Sliced... less than it could be.
From: Robert Jones (robertgbjones_at_[hidden])
Date: 2012-12-10 05:16:22

Hi Akira

An impressive body of work, which I've had reason to encounter in the past.
However I'm
a little confused: your proposal seems to date from 2005-2007, well before
Neil's Range 2.0
library, and yet seems in some ways to encompass and extend Neil's work.
Why was your
proposed work never taken up?

Thx, Rob.

On Mon, Dec 10, 2012 at 10:04 AM, Akira Takahashi
<faithandbrave_at_[hidden]>wrote:

> Hi, Robert
>
> 2012/12/10 Robert Jones <robertgbjones_at_[hidden]>
>
>> I was disappointed to discover that I can't write
>>
>> range | filtered( some_predicate ) | sliced( n, m ) | .....
>>
>> because sliced requires a random access range, and filtered produces a
>> forward range!
>>
>> Piffle.
>>
>> It seems such a useful and obvious use-case. Is this restriction really
>> necessary?
>>
>> Thx, Rob.
>>
>>
>
> I think this spec is unnecessity restriction.
> My OvenToBoost's "taken" and "dropped" adaptors requirement is
> SinglePassRange.
>
> http://dl.dropbox.com/u/1682460/git/OvenToBoost/libs/range/doc/html/range_extension/reference/range_adaptors/taken.html
>
> http://dl.dropbox.com/u/1682460/git/OvenToBoost/libs/range/doc/html/range_extension/reference/range_adaptors/dropped.html
>
> I can write follow:
> range | filtered(some_predicate) | dropped(n) | taken(m)
>
> This extension is now proposing to Boost.Range.
> I think "sliced" adaptor should be same requirements.
>
> >>========================
> Akira Takahashi
> site: https://sites.google.com/site/faithandbrave/about/en
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>

-- 
ACCU - Professionalism in programming - http://www.accu.org