https://svn.boost.org/trac10/ticket/5142 <p> type_erased Range Adaptor is in release brunch of Boost 1.46.0, but I feel that this is unnecessary. It is enough if there is any_range: </p> <pre class="wiki">#include &lt;iostream&gt; #include &lt;vector&gt; #include &lt;boost/assign/list_of.hpp&gt; #include &lt;boost/range/any_range.hpp&gt; #include &lt;boost/range/algorithm/for_each.hpp&gt; #include &lt;boost/range/adaptor/filtered.hpp&gt; typedef boost::any_range&lt; int , boost::forward_traversal_tag , int , std::ptrdiff_t &gt; integer_range; void disp(int x) { std::cout &lt;&lt; x &lt;&lt; std::endl; } void disp_all(integer_range r) { boost::for_each(r, disp); } bool is_even(int x) { return x % 2 == 0; } int main() { const std::vector&lt;int&gt; v = boost::assign::list_of(1)(2)(3)(4)(5); disp_all(v | boost::adaptors::filtered(is_even)); } </pre><p> Even if there is few it, I feel that I am premature to include it in 1.46.0 official release. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/5142 Trac 1.4.3 Akira Takahashi <faithandbrave@…> Mon, 31 Jan 2011 08:53:10 GMT https://svn.boost.org/trac10/ticket/5142#comment:2 https://svn.boost.org/trac10/ticket/5142#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> <p> I didn't feel it was too early to put this into the release branch. The core of the interface design is built upon experience gained with other any_iterator implementations. The implementation of any_interface has been tested in production environments successfully. The inclusion of the type_erased definitely has application particularly when chaining adaptors that are passing results to templatised range algorithms that are not specialised for any_range. </p> <p> At this point experience shows that the feature is popular and working. </p> Ticket faithandbrave@… Sun, 22 May 2011 12:57:30 GMT