Ordering for Futures and Objects

[bezirg]

For performance reasons, I do not provide Ord instances for Futures and Objects, e.g.:

{
 Fut<Unit> f1;
 Fut<Unit> f2;
 f1 == f2; // this is fine
 f1 < f2; // cannot compile
}

This means that futures and objects cannot be stored in fast Sets or being keys of fast Maps (elements are fine).

Could be potentially fixed by attaching to the future or object a thread-safe counter.

Equality for Futures&Objects is only provided.