On Wednesday, 26 March 2014 at 00:55:31 UTC, 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.
If you want to support web servers you should also consider
scenarios where you retrieve ranges from a distributed database
and the data arrive out-of-order. You can cut down on latency by
processing map() etc out-of-order.
