microsoft / microsoft/TypeScript
Inference from result of generic function no longer produces a union
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- PR merge metrics
- PR metrics pending
Description
### 🔎 Search Terms
function inference
### 🕗 Version & Regression Information
- This changed between versions 5.9 and 6.0-rc
### ⏯ Playground Link
[Playground Link](https://www.typescriptlang.org/play/?ts=6.0.0-dev.20260310#code/LAKAJgpgxgNghgJwgAgGYFcB2UAuBLAe02UggAcBRAR3ThgB4AVAPgAo5daYA1O9CAFzJGAGmQQAHmWg4IYXjH5DRyALYQAzhrgBzCAH4hGnAjyYdASiEA3AnjABuUJFiIUGbPiLIoBVWQ4cJjYCACMAK2UrYWRnCHJqLlZff0DWAG9kOCEAIgALCBgYAhyxUKEsSFQzOWQAXwsxdNBkVqzcgqKSkVAGpxA4hJo6DPbkfMLi0uRy5EqIasxauqaWtuzxzqmekD6gA)
### 💻 Code
```ts
declare function deepEqual(actualValue: T, expectedValue: T, message?: string): void;
declare function compact(obj: T): T
// Error
deepEqual(compact({ a: "hello", b: undefined }), {
a: "hello",
});
// Ok
deepEqual({ a: "hello", b: undefined }, {
a: "hello",
});
```
### 🙁 Actual behavior
First call fails. `T` for deepEqaul is inferred to `{ a: string, b: undefined;}` instead of `{
a: string;
b: undefined;
} | {
a: string;
b?: undefined;
}` as it is for the second call that succeeds. In 5.9, `T` is inferred to `{
a: string;
}` which is not really great either.
### 🙂 Expected behavior
Both calls should pass type checking
### Additional information about the issue
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.