Unbuffered range interface

[Joseph Rushton Wakeling]

On 26/03/14 01:55, Andrei Alexandrescu wrote:
> The recent discussion initiated by Walter points to a problem known since a long
> time ago: ranges are well modeled by objects in memory (arrays, lists, other
> containers) but poorly by objects that need to load or construct elements on the
> fly.

Is it important to distinguish here between stuff that is loaded/constructed on 
the fly and may differ, versus stuff that is constructed on the fly but 
deterministically, so that it's _as if_ the value was actually stored?