PanResponder.create() API either loses state or has stale state

Description

PanResponder has a bunch of private state. This means it's not safe to re-create during a gesture: that state would be lost. This means that it's important to keep a ref to PanResponder which is what the docs seem to suggest.

However, holding a ref to it is bad because all the props and state captured by handlers will be stale. To fix this, you have to either update parts of that ref manually, or to recreate the PanResponder instance (which, as mentioned earlier, will reset its state — which seems bad).

I think this says that PanResponder.create API is not a good API for Hooks and need to be revisited. E.g. maybe it should be a Hook like usePanResponder(config) which takes care of updating the appropriate event handlers as needed — or maybe implemented with useRef inside. The important part is that the handlers should always be fresh (and capture fresh values), while the internal state of the gesture recognizer should never be destroyed.

React Native Version

any version

Output of npx react-native info

irrelevant

Steps to reproduce

irrelevant

Snack, screenshot, or link to a repository

irrelevant

从 packages/react-native/Libraries/Interaction/PanResponder.js 开始，重点查看 issue 中描述的私有状态和 PanResponder.create API，并将其与文档中的 PanResponder 使用模式进行比较。确定如何在不破坏手势状态的情况下让处理器接收最新值；完成条件是就 API 方向达成一致，并确定状态保留和处理器时效性两方面对应的行为。