ref.current access lint rule broken by Typescript as type assertion

[yepitschunked]

We have some code which uses the useEvent RFC: https://github.com/reactjs/rfcs/blob/useevent/text/0000-useevent.md#internal-implementation

The original code (not exactly what we use, but close enough) passes the lint checks:

function useEvent(handler) {
  const handlerRef = useRef(null);

  // In a real implementation, this would run before layout effects
  useLayoutEffect(() => {
    handlerRef.current = handler;
  });

  return useCallback((...args) => {
    // In a real implementation, this would throw if called during render
    const fn = handlerRef.current;
    return fn(...args);
  }, []);
}

However, we've converted the code to TypeScript, and the returned useCallback has a type assertion:

  return useCallback((...args) => {
    // In a real implementation, this would throw if called during render
    const fn = handlerRef.current;
    return fn(...args);
-  }, []);
+  }, []) as T;
}

This breaks the lint rule, giving a Ref values (the current property) may not be accessed during render. (https://react.dev/reference/react/useRef) error.