Generic inference of Overloaded methods only working with the last defined method

Bug Report

🔎 Search Terms

• Generics
• Overload
• Type inference

🕗 Version & Regression Information

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

⏯ Playground Link

Playground link with relevant code

💻 Code

class SomeClazz {
    public overload(param: 'PARAM1'): number;
    public overload(param: 'PARAM2'): string;

    public overload(param: 'PARAM1' | 'PARAM2'): number | string {
        switch (param) {
            case 'PARAM1':
                return 1337;
            case 'PARAM2':
                return 'Hi';
        }
    }
}

function call<Ctx extends { [F in Name]: (this: Context, ...args: any[]) => any }, Name extends string>(
    ctx: Ctx,
    method: Name,
    ...args: Parameters<Ctx[Name]>
): void {
    ctx[method](...args);
}

const clazz = new SomeClazz();
clazz.overload('PARAM1'); // Works ok
clazz.overload('PARAM2'); // works ok
call(clazz, 'overload', 'PARAM1'); // ERROR: Argument of type '"PARAM1"' is not assignable to parameter of type '"PARAM2"'
call(clazz, 'overload', 'PARAM2'); // Works ok

Workbench Repro

🙁 Actual behavior

• Only one function overload is taken into account when inferring function parameter types

🙂 Expected behavior

• All function overloads should be taken into account when inferring function parameter types

Commencez par exécuter la reproduction liée dans Playground ou Workbench et comparez les deux sites d’appel génériques aux appels directs des surcharges. Suivez la manière dont Parameters<Ctx[Name]> est inféré pour la méthode surchargée ; c’est terminé lorsque call(clazz, 'overload', 'PARAM1') et call(clazz, 'overload', 'PARAM2') sont tous deux acceptés, tout en préservant le comportement de surcharge signalé.