opNext: Simplified ranges

[Sebastiaan Koppe]

On Sunday, 6 November 2022 at 21:08:10 UTC, Per Nordlöw wrote:
> It all boils down to fitting the design to the most common use 
> case. So is the most common case to be able to peek or not? I 
> really don't know right. Does anybody have any insights into 
> this?

I actually think the most lowest range should be one with 
destructive read semantics; non-peekable, non-copyable. You can 
build everything on top of that.

I also think ranges should be redesigned to have a 2 stage api. 
One to build the pipeline, one to iterate.