Anatoli Papirovski fe8794560a events: optimize condition for optimal scenario ...

Instead of always checking whether we've already warned about a
possible EventEmitter memory leak, first run the rest of the
code as accessing random properties on an Array is expensive.

In addition, remove an unnecessary truthy check.

PR-URL: https://github.com/nodejs/node/pull/20452
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>

2018-05-03 14:45:09 +02:00

..

ee-add-remove.js

events: optimize condition for optimal scenario

2018-05-03 14:45:09 +02:00

ee-emit.js

benchmark: (events) use destructuring

2018-01-23 01:29:30 +01:00

ee-listener-count-on-prototype.js

benchmark: (events) use destructuring

2018-01-23 01:29:30 +01:00

ee-listeners-many.js

benchmark: (events) use destructuring

2018-01-23 01:29:30 +01:00

ee-listeners.js

benchmark: (events) use destructuring

2018-01-23 01:29:30 +01:00

ee-once.js

benchmark: (events) use destructuring

2018-01-23 01:29:30 +01:00