Closed novusnota closed 5 months ago
Actually, this duplication of descriptions for !=
and ==
should be fixed. I think it makes sense to merge these two subsections together
Actually, this duplication of descriptions for
!=
and==
should be fixed. I think it makes sense to merge these two subsections together
Same can be said for >
and <
, >=
and <=
, +
and -
, etc. :)
Same can be said for > and <, >= and <=, + and -, etc. :)
not really -- those are a lot less polymorphic than ==
and !=
basically, I'm not a fan of maintaining two non-trivial lists of types for ==
and !=
==
and !=
T?
, but used "Optionals and null
value" instead)
Closes #173 (clarification of statements on implicit comparison) Closes #174 (better visibility of examples with comparing optionals)