Re: isInputRange instead of isForwardRange for std.algorithm.fill

[Andrei Alexandrescu]

On 5/17/12 2:14 AM, Guillaume Chatelet wrote:
It looks to me that isForwardRange is too much of a restriction for the
fill algorithm, isInputRange could do, we don't need any save() here or
am I missing something ?

That's correct, please file as a bug so we remember. (The second range 
must be forward in the overload fill(InputRange, ForwardRange) because 
it's iterated multiple times.)

Andrei