为何JavaFX的Node.setOnKeyPressed使用? super KeyEvent作为EventHandler泛型？

Great question! This is a perfect illustration of how Java generics' PECS (Producer-Extends, Consumer-Super) principle applies to real-world APIs like JavaFX. Let's break this down step by step to understand why the super wildcard is used here.

• The "Consumer" Role of EventHandler
  When you pass an EventHandler to setOnKeyPressed, that handler is going to consume a KeyEvent (or any parent type of KeyEvent, like InputEvent or Event). The PECS rule tells us that for code that takes in values (consumers), we should use ? super T to maximize flexibility while maintaining type safety.

• Reusability of Handlers
  Suppose you have a generic event handler that works for any Event—say, one that logs every event's timestamp:

  EventHandler<Event> eventLogger = event -> {
      System.out.println("Event fired at: " + System.currentTimeMillis());
  };
  

  If setOnKeyPressed only accepted EventHandler<KeyEvent>, you couldn't pass this eventLogger directly—you'd have to create a new handler specifically for KeyEvent that wraps it. But with EventHandler<? super KeyEvent>, this generic handler works perfectly, because KeyEvent is a subclass of Event, and the handler can safely consume it.

• Compatibility with Parent Event Types
  What if you have an EventHandler<InputEvent> that handles all input events (mouse, keyboard, etc.)? Since KeyEvent extends InputEvent, this handler is also compatible with setOnKeyPressed when using the super wildcard. This lets you reuse broader handlers for specific event types without rewriting redundant code.

• Avoiding Unnecessary Restrictions
  If the API used EventHandler<KeyEvent> instead, it would artificially restrict developers to only using handlers that explicitly declare KeyEvent as their type. The super wildcard removes this restriction, allowing any handler that can handle KeyEvent or any of its parent types to be used. This aligns with good API design principles—giving users more flexibility without sacrificing type safety.

At the end of the day, this design choice is all about making your code more flexible and reusable. By using ? super KeyEvent, JavaFX lets you leverage existing handlers for broader event types instead of forcing you to create redundant, type-specific handlers for every single event callback.

内容的提问来源于stack exchange，提问作者user5182503