21 Feb
2013
21 Feb
'13
10:44 a.m.
On Thu, Feb 21, 2013 at 12:55 AM, Neil Groves <neil@grovescomputing.com> wrote:
Since the solution I propose is not a new base-class it solves the problem both more completely and immediately. The users of Boost.Range would simply be encouraged to use the non-member function. In parallel the member function size() on iterator_range can be deprecated and subsequently removed.
Hmm, may I ask not to deprecate the member size()? Not that I have a special case that cannot be solved with the free size() function, it's just we have a lot of code that uses the member size(). Also, member size() looks a little bit more natural to me, although this is a matter of habit, I guess.