memo broken by new function props

Because memo only skips renders for primitive props

Because a new function reference is created on every render

Because React automatically invalidates memoized children after parent renders

Because callbacks are always treated as unstable by reconciliation