Cache events listeners descend too far down the "firing sequence" for "unfireable events"

[Chris Dennis]

Cache events listeners will get all the way to dispatching a task, including potentially spawning a thread , for events of a type for which there are no listeners. We have all the knowledge available to trim the call tree much sooner, and should be doing so.

[SamuelBussmann]

Is there anything I can do to support resolving this issue?