More tricky range semantics

[Joseph Rushton Wakeling via Digitalmars-d]

On Friday, 16 January 2015 at 17:22:42 UTC, Tobias Pankrath wrote:
> Ah, now I understand you. Since copy-construction is undefined 
> for ForwardRanges, you cannot guarantee this. Things would be 
> better, if we had required that this(this) does the same as 
> .save or must be @disabled.

I'm not sure I follow what you mean by this ... ?

> Than it would be clear that you either had to use a reference 
> or a pointer as argument to the function.

I don't see how that would affect the undesirable behaviour of 
the implementation.