Re: [boost] [Range] Confusing result of iterator_range::size()

Jeffrey Lee Hellrung, Jr. <jeffrey.hellrung <at> gmail.com> writes:

This came up just recently, e.g.,

http://comments.gmane.org/gmane.comp.lib.boost.devel/224758

Sorry, I miss it. Good discussion. And now we have my example with compilation error.

I think the end result was an agreement that

typedef typename boost::make_unsigned< difference_type >::type size_type

would be a valid definition of size_type, so the only argument against making the change that I can see is breaking existing code (probably unlikely...?) and...inertia.

I did not find authors of "Range" in the discussion. I am afraid your fix will be missed. It is good idea to write formal bug. Can you do it? Sergey Voropaev