Why does LongProperty implement Property b

Question

I have come across what seems like a peculiarity in the JavaFX API: LongProperty implements Property<Number>, but not Property<Long>.

What is the reason for this? I sort of get the idea that it all stems from Java's inherent problem with covariance and contravariance, because generics where implemented stupidly via erasure, to maintain backwards compatibility with the bytecode; but what problem could have arisen by having LongProperty implement both Property<Number> and Property<Long>?

Edit: This question originated from this problem: Apply LongProperty to TableColumn programmatically (vs semantically)

Answer 1

It can't implement both.

To do that, it would need to implement two versions of each method in the interface that uses the generic. Let's take one as an example:

bindBidirectional(Property<Long> other) { ... }

Under the hood, erasure means this gets compiled down to:

bindBidirectional(Property other) { ... }

So then, what would something that implements Property<Number> and Property<Long> do? It would have two methods:

bindBidirectional(Property<Long> other) { ... }
bindBidirectional(Property<Number> other) { ... }

... that would compile down, after erasure, to two methods:

bindBidirectional(Property other) { ... }
bindBidirectional(Property other) { ... }

These two methods conflict, and there'd be no way to resolve them at runtime.

Even if you used some compiler trickery to get around this, what happens when someone uses LongProperty as a raw Property?

Property rawLongProperty = new LongProperty();
rawLongProperty.bindBidirectional(someOtherRawProperty);

There's no way to know which of the two bindDirectional variants this is meant to resolve to.