什么<？超级虚空>是什么意思？

Question

I have encountered this class in code that I'm maintaining:

new GenericFutureListener<Future<? super Void>>() {...}

I'm having a really hard time understanding what this means. A Future containing a type that is either Void or its superclass - Object . So why not just write Future<Object> ?

Answer 1

Something nobody else pointed out: it's Netty and if you look at https://netty.io/4.0/api/io/netty/util/concurrent/class-use/Future.html you'll see there are some methods taking just this type in the library, eg ChannelPromise.addListener(GenericFutureListener<? extends Future<? super java.lang.Void>> listener) . And these methods have this signature because of the generic case: Future.addListener(GenericFutureListener<? extends Future<? super V>> listener) . ChannelPromise merely extends Future<Void> .

The generic case makes sense because 1. if you have a FutureListener<Future<Object>> , it can handle any Object value when a future completes; 2. since a V is an Object it can handle V . Thus it can listen to a Future<V> . Obviously the same holds for any supertype of V instead of Object .

Of course, these signatures would be much simpler if Java had declaration-site variance , but it doesn't and probably won't any time soon.

Answer 2

It looks like this is being created to conform to some generic type like GenericFutureListener<Future<? super T>> GenericFutureListener<Future<? super T>> , which is not flexible enough to allow for GenericFutureListener<Future<Void>> alone.

For instance if you have something like this:

class GenericFutureListener<T> {}

public static <T> void m(GenericFutureListener<Future<? super T>> p) {
    ...
}

m(new GenericFutureListener<Future<? super Void>>() {}); // works,
m(new GenericFutureListener<Future<Void>>() {}); // does not work

Passing in just a GenericFutureListener<Future<Void>> is not allowed.

Answer 3

As you've noted, this Future<? super Void> Future<? super Void> can only be a void future, or Object future.

But:

So why not just write Future?

The intention of the developer was almost certainly to limit "listeners" to void actions. But if one allowed Future<Object> , then any other type could be used as the Future 's value, because a Future<Object> could hold a String (or any other type) result.

java.lang.Void being a final class, it doesn't allow any child classes, which effectively almost completely limits it to void actions (unless one has practical value in calling new Object() when setting the result of the future)

Answer 4

Yes, you can use a Future<Object> with that Listener, but the declaration makes it clear that the Listener should/does not use the result.

Declaring this as GenericFutureListener<Future<Object>> gives the impression the Listener does something with the result.

Answer 5

Sometimes we only care about the task has done or not.

Someone (like me) may prefer to return Future<Void> to indicate that the task has no result.

While someone else may prefer to use Future<Object> or Future<?> and use null as the result.

I think this guy encountered both Future<Void> and Future<Object> . So he use Future<? super Void> Future<? super Void> to adapt both generic.