Argument becomes implicit any when a void-returning overload follows a non-void-returning signature

Bug Report

🔎 Search Terms

overload argument type signature

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about overloads (and #48077)

⏯ Playground Link

Playground link with relevant code

💻 Code

declare const it: {
    (test: () => Promise<void>): void;
    (test: (input: string) => void): void;
}

it((input) => {
    input.toUpperCase();
});

it(async () => {
    // ..
});

🙁 Actual behavior

Error: Parameter 'input' implicitly has an 'any' type.

🙂 Expected behavior

No type error. The input parameter is type string and should be resolved as such.

For more context, see https://github.com/DefinitelyTyped/DefinitelyTyped/pull/59075.

[RyanCavanaugh]

The problem is that we assign a contextual type during overload resolution, and don’t have an acceptable way to “undo” that. Prior attempts to fix this have failed for one reason or another.

See also #11936

[JoshuaKGoldberg]

Hmm, now that #29374 is in I was looking forward to making another multi-year pull request. Great…!