Wrong spread parameters type inference in function with all spread parameters overloads

Bug Report

🔎 Search Terms

overload tuple spread

⏯ Playground Link

Playground link with relevant code

💻 Code

type A<K extends [any], V extends [any]> =
  & { (...args: [...K]): void }
  & { (...args: [...K, ...V]): void }

// Now: (parameter) args: ([...K][0] | [...K, ...V][0])[]
// Expected: (parameter) args: [...K] | [...K, ...V]
const f = <K extends [any], V extends [any]>(): A<K, V> => (...args) => {}

🙁 Actual behavior

args have type ([...K][0] | [...K, ...V][0])[]

🙂 Expected behavior

args have type [...K] | [...K, ...V]

Start with the linked TypeScript Playground and reduce the example while preserving the overloads with tuple spreads. Trace how the compiler infers the rest parameter for the intersected call signatures, then add a regression test covering the shown actual and expected types; done means args is inferred as the tuple union rather than an array of element unions.