Hi Akira<div><br></div><div>An impressive body of work, which I&#39;ve had reason to encounter in the past. However I&#39;m</div><div>a little confused: your proposal seems to date from 2005-2007, well before Neil&#39;s Range 2.0</div>

<div>library, and yet seems in some ways to encompass and extend Neil&#39;s work. Why was your</div><div>proposed work never taken up?</div><div><br></div><div>Thx, Rob.</div><div><br><br><div class="gmail_quote">On Mon, Dec 10, 2012 at 10:04 AM, Akira Takahashi <span dir="ltr">&lt;<a href="mailto:faithandbrave@gmail.com" target="_blank">faithandbrave@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Robert<br><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">2012/12/10 Robert Jones <span dir="ltr">&lt;<a href="mailto:robertgbjones@gmail.com" target="_blank">robertgbjones@gmail.com</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I was disappointed to discover that I can&#39;t write
<div><br></div><div><font face="courier new, monospace">range | filtered( some_predicate ) | sliced( n, m ) | .....</font></div><div><br></div><div>because sliced requires a random access range, and filtered produces a forward range!</div>




<div><br></div><div>Piffle.</div><div><br></div><div>It seems such a useful and obvious use-case. Is this restriction really necessary?</div><div><br></div><div>Thx, Rob.</div><div><br></div></blockquote></div><div><br></div>


<div class="gmail_extra"><br></div></div></div><div class="gmail_extra">I think this spec is unnecessity restriction.</div><div class="gmail_extra">My OvenToBoost&#39;s &quot;taken&quot; and &quot;dropped&quot; adaptors requirement is SinglePassRange.</div>


<div class="gmail_extra"><a href="http://dl.dropbox.com/u/1682460/git/OvenToBoost/libs/range/doc/html/range_extension/reference/range_adaptors/taken.html" target="_blank">http://dl.dropbox.com/u/1682460/git/OvenToBoost/libs/range/doc/html/range_extension/reference/range_adaptors/taken.html</a><br>


</div><div class="gmail_extra"><a href="http://dl.dropbox.com/u/1682460/git/OvenToBoost/libs/range/doc/html/range_extension/reference/range_adaptors/dropped.html" target="_blank">http://dl.dropbox.com/u/1682460/git/OvenToBoost/libs/range/doc/html/range_extension/reference/range_adaptors/dropped.html</a><br>


</div><div class="gmail_extra"><br></div><div class="gmail_extra">I can write follow:</div><div class="gmail_extra">range | filtered(some_predicate) | dropped(n) | taken(m)<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">


This extension is now proposing to Boost.Range.</div><div class="gmail_extra">I think &quot;sliced&quot; adaptor should be same requirements.</div><br>&gt;&gt;========================<span class="HOEnZb"><font color="#888888"><br>

Akira Takahashi<br>site: <a href="https://sites.google.com/site/faithandbrave/about/en" target="_blank">https://sites.google.com/site/faithandbrave/about/en</a><br>

</font></span></div>
<br>_______________________________________________<br>
Boost-users mailing list<br>
<a href="mailto:Boost-users@lists.boost.org">Boost-users@lists.boost.org</a><br>
<a href="http://lists.boost.org/mailman/listinfo.cgi/boost-users" target="_blank">http://lists.boost.org/mailman/listinfo.cgi/boost-users</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>ACCU - Professionalism in programming - <a href="http://www.accu.org">http://www.accu.org</a><br>


</div>