Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #28357
Currently, the
EventListener
interface is invariant. As a result, functions that pass a subtype ofEvent
fail to compile (e.g. see theCustomEvent
andMessageEvent
examples below).CustomEvent handler
MessageEvent handler
As a result, it seems like a lot of people resort to using the
as EventListener
type assertion.Instead of having users resort to the
as
operator, I'm proposing we introduce a generic type variable that extendsEvent
to theEventListener
interface. We could then pass the appropriate sub-type to theaddEventHandler
functions for the respective objects (e.g.EventSource
below).The net result would be to allow users to simply do:
11/19/19: Note that the PR currently only implements the changes for the
EventSource
interface. I'd like to get some feedback before porting the change to every other object.