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

Subject: Re: [boost] [Range] Confusing result of iterator_range::size()
From: Olaf van der Spek (ml_at_[hidden])
Date: 2011-11-03 11:15:22

On Thu, Nov 3, 2011 at 2:51 PM, Thorsten Ottosen
<thorsten.ottosen_at_[hidden]> wrote:
> Den 03-11-2011 13:16, Olaf van der Spek skrev:
>
>>> If you can find it, I might believe you. It should be in the archieves
>>> from
>>> some years ago.
>>
>> I meant the discussion last month.
>> Didn't know it was discussed before. Do you have any idea in what
>> year/month?
>
> A couple of years maybe. I think it happened at the same time we demanded
> that size(Rng) only worked for RandomAccessRanges and that this function
> also returns a signed type.

IMO the same arguments apply to that function.

> Using the old docs, one can probably track down the approximate time.
>
> The bottom line is that it was a deliberate decision. The example put
> forward
>
>  std::min(bbb.size(), (size_t)arr.size());
>
> is not portable either.

My concern was about a.size() < b.size() where one size() returns a
signed type and the other an unsigned type.

What about ptr_range?
-- 
Olaf