Microsoft/TypeScript
Vedi su GitHubNested generic calls don't inherit outer inferences when their return types are intersections containing functions
Open
#58.833 aperta il 12 giu 2024
Domain: IntersectionHelp WantedPossible Improvement
Metriche repository
- Star
- (48.455 star)
- Metriche merge PR
- (Merge medio 6g 17h) (9 PR mergiate in 30 g)
Descrizione
🔎 Search Terms
generic call inference intersection return type
🕗 Version & Regression Information
- This is the behavior in every version I tried
⏯ Playground Link
💻 Code
interface Config<T> {
context: T;
invoke: {
(x: T): void;
exec: (x: T) => void;
};
}
declare function create<T>(config: Config<T>): void;
declare function myInvokeBroken<T>(i: { exec: (x: T) => void }): {
(x: T): void;
} & typeof i;
create({
context: { count: 3 },
invoke: myInvokeBroken({
exec: (x) => {
x
// ^?
x.count.toFixed(2);
},
}),
});
declare function myInvoke<T>(i: { exec: (x: T) => void }): {
(x: T): void;
exec: (x: T) => void;
};
create({
context: { count: 3 },
invoke: myInvoke({
exec: (x) => {
x
// ^?
x.count.toFixed(2);
},
}),
});
🙁 Actual behavior
x doesn't get contextually typed based on the outer inferences in the myInvokeBroken example
🙂 Expected behavior
I would expect myInvokeBroken and myInvoke to work here in the same way. Their return types are the same. It's only that myInvokeBroken is using an intersection in its return type while myInvoke isn't
Additional information about the issue
No response