The last example says it can't be written in Reselect, but it can.

[todorpr]

I just discovered proxy-memoize recently I think it has a good potential.

One thing I think is incorrect is the statement that the last example can't be written in reselect

The last example is this one:

const todoTextsSelector = memoize(state => state.todos.map(todo => todo.text));

Here is how I see it in reselect:

const state = {
  todos: [{ text: 'aaa' }, { text: 'bbb' }]
}

const todoTextSelector = createSelector(
  state => state.todos,
  todos => todos.map(todo => todo.text)
)

console.log(todoTextSelector(state)) // ["aaa", "bbb"]
console.log(todoTextSelector(state)) // ["aaa", "bbb"]
console.log(todoTextSelector(state)) // ["aaa", "bbb"]
console.log(todoTextSelector(state)) // ["aaa", "bbb"]
console.log(todoTextSelector.recomputations()) // 1

[dai-shi]

Thanks for jumping in.

My apologies, that was too easy without detailed info.

const state = {
  todos: [{ text: 'aaa', completed: true }, { text: 'bbb', completed: false }]
}

We assume this case, and when only completed is changed.

Please refer this too: reduxjs/react-redux#1653 (comment)

[todorpr]

Aha, now I get it. You are absolutely right - reselect's selector will recompute in this case, whereas memoize's won't.