Microsoft/TypeScript
在 GitHub 查看Signatures with less parameters aren't assignable to compatible targets with more when their rest param is an instantiated `NoInfer`
Open
#59,668 建立於 2024年8月17日
Domain: check: Type InferenceHelp WantedPossible Improvement
倉庫指標
- Star
- (48,455 star)
- PR 合併指標
- (平均合併 6天 17小時) (30 天內合併 9 個 PR)
描述
🔎 Search Terms
NoInfer signature parameters list rest
🕗 Version & Regression Information
- This is the behavior in every version I tried
⏯ Playground Link
💻 Code
declare function call<A extends readonly unknown[]>(
arg: (...args: NoInfer<A>) => void,
...args: A
): A;
// Argument of type '(a: number) => void' is not assignable to parameter of type '(...args: NoInfer<[number, number]>) => void'.
// Types of parameters 'a' and 'args' are incompatible.
// Type '[number, number]' is not assignable to type '[a: number]'.
// Source has 2 element(s) but target allows only 1.(2345)
const inferred = call((a: number) => {}, 1, 2);
// ^? function call<[number, number]>(arg: (...args: NoInfer<[number, number]>) => void, args_0: number, args_1: number): [number, number]
declare function call2<A extends readonly unknown[]>(
arg: (...args: A) => void,
...args: A
): A;
const inferred2 = call2<[number, number]>((a: number) => {}, 1, 2);
// ^? const inferred2: [number, number]
🙁 Actual behavior
The first call fails to typecheck
🙂 Expected behavior
Both of those calls use the same arguments. The first one is using NoInfer so the covariant inference can get prioritized. That prevents the instantiated signature from typechecking like the second one. Note that the first call infers the same type argument as the one that is supplied explicitly to the second call: [number, number]
Additional information about the issue
I think that this can be fixed by normalizing NoInfer<[A, B]> to [NoInfer<A>, NoInfer<B>]. This would be similar to what instantiateMappedTupleType does today at times.