D3 sumtype api

[Dejan Lekic]

On Friday, 28 February 2025 at 11:51:47 UTC, Paul Backus wrote:
> Now, you might say, "who cares about those edge cases; just 
> give me the simple implementation that works most of the time." 
> But that's also how `Nullable` started out, and it turns out 
> people cared enough about the edge cases to go in and add 
> support for them. Since we already know that the demand exists, 
> it seems prudent to have v3's `Option` support these edge cases 
> from the beginning.

In my view Nullable is fundamentally wrong (I have to call 
nullify() - whaaaat?), and if something else is based on 
something that is fundamentally wrong, it will most likely also 
be fundamentally wrong.

I mean no disrespect, I am giving you an honest opinion here. I 
do not use Nullable simply because I can't assign null to it - it 
simply does not make sense to use something with name 'Nullable' 
and not being able to assign null to it, so I do not use it. I 
will most likely have the same issue with Option!T, judging from 
your last reply...