Range Redesign: Copy Semantics

[Richard (Rikki) Andrew Cattermole]

On 21/01/2024 11:58 PM, Jonathan M Davis wrote:
> Either way, if we're doing a new major version of Phobos, we'll be reworking
> a variety of stuff anyway, and so Nullable would presumably be on the list
> (e.g. I think that it was a big mistake to make it a range, and I'd remove
> that functionality; slicing it to get a range is one thing, but the fact
> that it itself is a range definitely causes problems in generic code).

Umm, why would we bring back Nullable?

By then we'd have sum types which can represent it in the language far 
better.