Currently LambdaMultipleChangeListenerHandler maintains a list of all registered consumers. These consumers are executed in the order they are registered.
Since Consumer already supports chaining of method calls using Consumer::andThen, we should consider using it instead of maintaining a list of consumers.
The chained Consumer may be returned when unregistering change listener (JDK-8151617).
Since Consumer already supports chaining of method calls using Consumer::andThen, we should consider using it instead of maintaining a list of consumers.
The chained Consumer may be returned when unregistering change listener (
- relates to
-
JDK-8151617 SkinBase: missing unregisterChangeListener
- Resolved