This pull request seeks to resolve an issue where memoized selector cache clearing occurs more frequently than anticipated, due to the internal behavior of the underlying rememo library.

Given the following scenario, the cache for getBlock would be cleared on every single invocation:

for ( i = 0; i < 100; i++ ) {
	getBlock( state, i % 2 ? aBlockUID : bBlockUID );
}

This is because memoization compares the result of the dependents between invocations, and in the above case, blocksByUid[ uid ] will produce different results:

https://github.com/aduth/rememo/blob/11644c10d5bb6fa041c387c9ce9e6c26604d3556/es/index.js#L86-L90

As the maintainer of rememo, unless compelling arguments are made otherwise, I plan to release a subsequent major release dropping support for all but the state argument in getDependants (the second argument of createSelector).

Testing instructions:

Verify that unit tests pass:

npm run test-unit