microsoft / microsoft/TypeScript
ts2556 is too restrictive when generics are involved
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
🔎 Search Terms
"generic", "tuple", "spread", "rest", "ts2556", "a spread argument must either have a tuple type or be passed to a rest parameter"
🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about spreading into argument lists
⏯ Playground Link
💻 Code
declare const f: () => void
declare const x: readonly []
f(...x) // works
const test = <T extends readonly []>(x: T) =>
f(...x) // does not work
🙁 Actual behavior
Attempting to spread a generically-typed value whose constraint guarantees tuple-ness into a compatible argument list is forbidden.
🙂 Expected behavior
I should be allowed to do this.
Additional information about the issue
Possibly-related issues:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the generic tuple-spread example in the linked TypeScript Playground and compare it with the non-generic case that succeeds. Trace the compiler path that reports TS2556 for spreads into argument lists, then add coverage showing the constrained generic case is accepted while incompatible spreads remain rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100