Microsoft/TypeScript
Voir sur GitHubIndexing tuple intersection type beyond length produces unexpected type
Open
#42 557 ouverte le 30 janv. 2021
BugDomain: IntersectionHelp Wanted
Métriques du dépôt
- Stars
- (48 455 stars)
- Métriques de merge PR
- (Merge moyen 6j 17h) (9 PRs mergées en 30 j)
Description
Bug Report
🔎 Search Terms
tuple intersection index type
⏯ Playground Link
💻 Code
type T = [number, boolean] & { x: string };
declare const t: T;
const a = t[0]; // number
const b = t[1]; // boolean
const c = t[2]; // number | boolean !?
🙁 Actual behavior
c is typed as number | boolean
🙂 Expected behavior
c should be typed as undefined
I'm not sure if this is a bug, or intended behavior. But it was surprising. If the type is just a tuple, indexing beyond its length produced undefined. But if it is part of an intersection, the element type is changed to number | boolean, as if it is no longer a tuple, but an array. However, indexing 0 or 1 still produces the correct type for those element positions.