equals looks fishy

[treeowl]

If I set potato = unknown(); then potato.equals(potato) should be true, but @Override @SuppressWarnings({"EqualsWhichDoesntCheckParameterClass"}) public boolean equals(Object obj) { return false; } seems to say otherwise.

[npryce]

The semantics of unknown is like that of NULL in SQL or floating point NaN. It represents a value that is not known, rather one that is known not to exist. If you want a "known-to-be-nonexistent" value, fork the code and change it to behave the way you want.