https://svn.boost.org/trac10/ticket/9684 <p> I think a multidimensional (floating point) counting_range with configurable step size would be useful, at least I have found a need for that many times. Here is a suggestion, could something like this eventually be included in boost? What modifications should I make (after switching to boost::bind)? The iterated values are evenly spaced from each other and the boundaries. </p> <p> Example usage: </p> <p> boost::array&lt;double, 2&gt; start{-4, 3}, end{4, 11}; </p> <p> const size_t samples_per_dim = 2; </p> <p> for (const auto&amp; i: volume_iterator(start, end, samples_per_dim)) { </p> <blockquote> <p> print(i); </p> </blockquote> <p> } </p> <p> Output: </p> <p> -2 5 </p> <p> 2 5 </p> <p> -2 9 </p> <p> 2 9 </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9684 Trac 1.4.3 ilja.j.honkonen@… Wed, 19 Feb 2014 16:54:56 GMT https://svn.boost.org/trac10/ticket/9684 https://svn.boost.org/trac10/ticket/9684 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">testi.cpp</span> </li> </ul> Ticket Neil Groves Wed, 26 Feb 2014 22:08:19 GMT https://svn.boost.org/trac10/ticket/9684#comment:1 https://svn.boost.org/trac10/ticket/9684#comment:1 <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> irange with step size already exists. The floating-point idea has been explicitly rejected due to difficulties providing loop variant / invariant guarantees. </p> Ticket anonymous Thu, 27 Feb 2014 03:49:49 GMT