Adding an overload to .filter breaks specific inference with nested functions

🔎 Search Terms

"filter inference overload", "filter boolean"

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about inferred types

⏯ Playground Link

https://tsplay.dev/wQbrvN

💻 Code

type NonFalsy<T> = T extends false | 0 | "" | null | undefined | 0n
    ? never
    : T;

// Comment this out
interface Array<T> { filter(predicate: BooleanConstructor, thisArg?: any): NonFalsy<T>[]; }

const id = <T,>() => (t: T) => !!t;

['foo', 'bar'].filter(id())
//                    ^?

🙁 Actual behavior

Nested function inference works (type parameter is string) without the additional overload, and fails (type parameter is unknown) with the overload (even though the added overload isn't the one in use).

🙂 Expected behavior

Nested function inference should work regardless of whether an overload is added to .filter or not.

Additional information about the issue

Adding the overload is described in https://github.com/microsoft/TypeScript/issues/50387 and made popular by ts-reset.
It's possible the overload order may matter in this instance, but difficult to test when the main overloads are coming from lib definitions.

Reproduisez le comportement dans le TypeScript Playground lié, en comparant l’inférence avec et sans la surcharge Array.filter BooleanConstructor ajoutée. Lisez les définitions lib pertinentes ainsi que le contexte de l’ordre des surcharges dans l’issue #50387 ; le travail est terminé lorsque l’inférence des fonctions imbriquées continue d’inférer string pour l’exemple lorsque la surcharge est présente.