Call signatures of union types

[DickvdBrink]

TypeScript Version: 1.8.4

Code

type stringType1 = "foo" | "bar";
type stringType2 = "baz" | "bar";

interface Temp1 {
 getValue(name: stringType1);
}

interface Temp2 {
 getValue(name: stringType2);
}

function test(t: Temp1 | Temp2) {
 var z = t.getValue("bar"); // Error here
}

Expected behavior:
I was hoping everything would go fine (which is the case when I only use one interface in the function test

Actual behavior:
I get an error: "Cannot invoke an expression whose type lacks a call signature". Is this by design?

[Igorbek]

t can be Temp2. Temp2.getValue accept name that can be either "bar" or "baz", not "foo".

[RyanCavanaugh]

This is currently by design because we don't synthesize an intersectional call signature when getting the members of a union type -- only call signatures which are identical appear on the unioned type.

To make this work, we'd need some plausible algorithm that takes two sets of signatures and produces one (or many?) new signatures that are substitutes for the original.

interface Alpha {
 (x: string): void;
 (y: number, z: string): void;
}

interface Beta {
 (...args: Array<number|string>): boolean;
}

interface Gamma {
 (y: string|number, z: any): string;
}

let ab: Alpha | Beta;
let ac: Alpha | Gamma;
let bc: Beta | Gamma;

// What arguments can I invoke ab, ac, and bc with?

[zpdDG4gta8XKpMCd]

Dick van den Brink (@DickvdBrink) getting an error (albeit a different one) the way you laid out your example is a completely expected thing:

foo is only an option for one of 2 possible methods, all equal there is a change that foo is going to go to an instance of Temp2 which cannot be accepted by its getValue method, hence the compile error (different from what you got)

[DickvdBrink]

Aleksey-Bykov, you are correct - I made a mistake when creating the example - updated it.
The point of this issue was that I expected it to work with bar but it didn't.