Re: Unbuffered range interface

2014-03-29 Thread Marco Leise
I see it like Dimitry and have actually implemented what he describes a while ago. It is a one consumer, one producer circular buffer which offers a sliding window into the content. As typical for a stream(!) it operates on variable blocks of bytes and producer and consumer never actually

Re: Unbuffered range interface

2014-03-28 Thread QAston
On Friday, 28 March 2014 at 19:21:51 UTC, QAston wrote: What set of primitives would work best for all these scenarios and more? class Silver { enum bullet = true; } Woops, I should have posted golden hammer, sorry.

Re: Unbuffered range interface

2014-03-28 Thread QAston
What set of primitives would work best for all these scenarios and more? class Silver { enum bullet = true; }

Re: Unbuffered range interface

2014-03-27 Thread Dmitry Olshansky
26-Mar-2014 04:55, Andrei Alexandrescu пишет: 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. Here

Re: Unbuffered range interface

2014-03-27 Thread 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

Re: Unbuffered range interface

2014-03-26 Thread Vladimir Panteleev
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

Re: Unbuffered range interface

2014-03-26 Thread Andrea Fontana
Similar scenario writing my mongodb (document based db) wrapper. 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,

Unbuffered range interface

2014-03-25 Thread Andrei Alexandrescu
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. Here are some scenarios that we need to

Re: Unbuffered range interface

2014-03-25 Thread Ola Fosheim Grøstad
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