Range Redesign: Copy Semantics

[monkyyy]

On Sunday, 21 January 2024 at 05:00:31 UTC, Jonathan M Davis 
wrote:
> wall-o-text

Can this be summarized as

```d
enum isRangeCopible(R)= is(
   (R r){
     R rdup=r;
     r=rdup;
   }
);
```

> What I'd like to get out of this thread is feedback on how much 
> sense this idea does

I think someone formal should collect all changes people want to 
make to ranges

see my thread for .index and feature sets
theres something about immutablity
I would also suggest arrays should be more important then doubly 
linked lists