Does `dispatch` function identity change when passed in context? [Re: eslint-plugin-react-hooks]

Issue:

• The docs for useReducer suggests omitting dispatch from the dependencies list of useEffect and useReducer.

  Note
  React guarantees that dispatch function identity is stable and won't change on re-renders. This is why it's safe to omit from the useEffect or useCallback dependency list.

• The docs also recommend passing dispatch function from useReducer via context to avoid passing callbacks down a large component tree:

• eslint-plugin-react-hooks warns if dispatch (that's been passed from context) is not added to useEffect dependencies list.

  This conflicts with the first point above (docs suggesting omitting dispatch from the dependencies list)

  React Hook useCallback has a missing dependency: 'dispatch'. Either include it or remove the dependency array.
  

Is this:

• Expected behavior after passing dispatch through context - so the docs should have a small amendment for this scenario?
• Or a bug in eslint-plugin-react-hooks?

Thanks for the help!!

Working Sample:

• Example Sandbox: https://codesandbox.io/s/vnq10rmwjy

Read the linked useReducer and Hooks FAQ documentation first, then reproduce the warning in the CodeSandbox and compare it with eslint-plugin-react-hooks behavior. Done means determining whether the docs need clarification or the plugin behavior needs a separate fix, with the relevant conclusion recorded.