https://issues.dlang.org/show_bug.cgi?id=14804
Basile-z changed:
What|Removed |Added
CC|b2.t...@gmx.com |
--
https://issues.dlang.org/show_bug.cgi?id=14804
Jack Stouffer changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://issues.dlang.org/show_bug.cgi?id=14804
Luís Marques changed:
What|Removed |Added
CC||l...@luismarques.eu
--- Comment #4 from Luís
https://issues.dlang.org/show_bug.cgi?id=14804
b2.t...@gmx.com changed:
What|Removed |Added
See Also||https://issues.dlang.org/sh
https://issues.dlang.org/show_bug.cgi?id=14804
--- Comment #3 from b2.t...@gmx.com ---
(In reply to monkeyworks12 from comment #2)
> but let's not close this one for opEquals.
Without great convictionI've opened the PR, but let's the official maintainers
take the decision ;)
https://github.com/D
https://issues.dlang.org/show_bug.cgi?id=14804
--- Comment #2 from monkeywork...@hotmail.com ---
I agree opCmp is a little weird to implement for Nullable, but it's really not
much different from NaN. If we follow what the floating point numbers do:
Nullable!int n1;
Nullable!int n2 = 0;
assert(!
https://issues.dlang.org/show_bug.cgi?id=14804
b2.t...@gmx.com changed:
What|Removed |Added
CC||b2.t...@gmx.com
--- Comment #1 from b2.t...