Forward Range(s)

[Era Scarecrow]

On Monday, 27 August 2012 at 20:46:18 UTC, Jonathan M Davis wrote:
> I don't think that I really understand the question, but I'd be 
> worried about intermixing save with operating on a range as an 
> output range. It _should_ work, but save was designed with 
> reading in mind, not writing. An output range doesn't have to 
> have save or even front or popFront. All it needs is to work 
> with put. Output ranges are a very different beast from input 
> ranges, even if input ranges can be output ranges.
>
> That being said, I'd expect that save would save the current 
> state, and any writing to the original would not affect the 
> saved range.

  Well the first block actually holds size information and the 
information it holds is the old information, stuff may have been 
added or taken away, so hopefully not to have to do two passes (a 
dummy pass and then a real one) I was hoping save would save the 
location. If it doesn't reference the previous location using the 
current data then I'll need to figure something out.

  It's this that's been holding off one of my projects for a while 
as I'm not sure how to best approach it.