microsoft / microsoft/TypeScript
A[] form works, but Array<A> breaks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.4k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
Bug Report
🔎 Search Terms
site:github.com inurl:/microsoft/TypeScript/issues/ Array [] normalization syntactic sugar
🕗 Version & Regression Information
This works in 3.9.7, broke in 4.0.5, and remains broken in Nightly.
- This changed between versions 3.9.7 and 4.0.5
⏯ Playground Link
Playground link with relevant code
💻 Code
type R<C> = [C, ...R<C>[]] | number; // works, as expected
type S<C> = [C, ...Array<S<C>>] | number; // fails unexpectedly - should work identically
const r: R<"add"> = ["add", 2, 1];
const s: S<"add"> = ["add", 2, 1];
🙁 Actual behavior
The A[] form in the first line works, but the otherwise-identical Array<…> form on the second line breaks with the warning Type alias 'S' circularly references itself.(2456).
🙂 Expected behavior
Both of these should work, and behave identically, as they are merely syntactic sugar for each other.
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 with the linked Playground examples and the minimal R and S type aliases, comparing behavior between TypeScript 3.9.7, 4.0.5, and Nightly. Trace the circular type-alias check and its handling of Array versus T[]; done means both equivalent recursive aliases compile without the circular-reference diagnostic.
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
- 38/100