Pipe function + `React.memo` returns component with `any` props

TypeScript Version: 3.9.2

Search Terms: generic pipe pipeWith react memo HOC props any

Code

import * as React from 'react';

declare function pipeWith<A, B>(a: A, ab: (a: A) => B): B;

type Props = { foo: number };
declare const MyComponent: React.FunctionComponent<Props>;

// ✅ correct props type
// React.NamedExoticComponent<Props>
const r1 = React.memo(MyComponent);

// ❌ `any` props type
// React.MemoExoticComponent<React.ComponentType<any>>
const r2 = pipeWith(MyComponent, React.memo);

// Workaround
// ✅ correct props type
// React.NamedExoticComponent<Props>
const r3 = pipeWith(MyComponent, (C) => React.memo(C));

Using latest version of @types/react (at the time of writing: 16.9.35).

Expected behavior:

See above.

Actual behavior:

See above.

Playground Link:

https://stackblitz.com/edit/react-ts-4ih6jn

Related Issues:

https://github.com/microsoft/TypeScript/issues/25637, although that was closed as a duplicate of an issue which has since been closed (https://github.com/microsoft/TypeScript/issues/10957), so I decided to post a new issue.

Beginne mit dem StackBlitz-Reproduzierer und dem generischen pipeWith-Beispiel und vergleiche React.memo(MyComponent) mit pipeWith(MyComponent, React.memo). Lies das Verhalten der TypeScript-Typinferenz im Zusammenhang mit der React.memo-Deklaration aus @types/react 16.9.35. Erledigt ist die Aufgabe, wenn das Ergebnis der Pipeline Props statt any ableitet und dabei das Verhalten des direkten Aufrufs beibehält.