Range Redesign: Copy Semantics

[Paul Backus]

On Wednesday, 24 January 2024 at 17:35:32 UTC, Paul Backus wrote:
> In general, we should not make assumptions in our library code 
> unless we are capable of enforcing them. Since we are, 
> unfortunately, not capable of enforcing the assumption that all 
> copyable ranges have forward-range semantics, we should not 
> allow ourselves make it.

Having thought about it some more, this is a bad argument, and I 
withdraw it.

The entire range API is based on convention to begin with. Of 
course there's no enforcement mechanism!