microsoft / microsoft/TypeScript
for-of loop with intersection of array types produces a union of element types
还没有人认领这个 Issue。
- 主要语言
- Go
- 星标
- 111k
- 派生
- 14.3k
- 平均合并
- 1 天 19 小时
- 30 天内合并 PR
- 117
描述
TypeScript Version: 3.9.2, 4.0.0-beta
Search Terms: intersection, for-of, union, iterable, iterator, iterate, array
Expected behavior:
When you use a for..of loop to iterate over the elements of an intersection of arrays (or maybe other iterables), what type should the elements be? I would expect either:
- you get the same type as when you index into the array: an intersection of the element types; or
- you get the same type as when you use the iterator method manually: the first element type because the iterator methods are overloads.
Actual behavior:
Iterating over an intersection of arrays with a for..of loop produces a union of their element types for some reason.
Related Issues:
#11961: intersection of array types results in overloaded methods (this would maybe imply overloaded iterators, but that's not happening here)
Aside:
I'm not sure why you'd want an intersection of array types in the first place; but the behavior showed up in a Stack Overflow question and I'm at a loss understanding why we get a union here.
Code
declare const arr: Array<{ a: string }> & Array<{ b: number }>;
for (const elemItr of arr) {
// { a: string } | {b : number } 😕
elemItr.a.toUpperCase(); // error!
elemItr.b.toFixed(); // error!
}
// I expected either this (intersection of element types)
const elemIdx = arr[0]; // { a: string; } & { b: number; }
elemIdx.a.toUpperCase(); // okay
elemIdx.b.toFixed(); // okay
// or this (overloaded iterators giving the first element type only)
const iter = arr[Symbol.iterator];
/* const iter: {
(): IterableIterator<{ a: string }>;
(): IterableIterator<{ a: string }>;
} & {
(): IterableIterator<{ b: number }>;
(): IterableIterator<{ b: number }>;
} */
const result = arr[Symbol.iterator]().next();
if (!result.done) {
result.value.a.toUpperCase(); // okay
result.value.b.toFixed(); // error, expected this
}
Output
"use strict";
for (const elemItr of arr) {
// { a: string } | {b : number } 😕
elemItr.a.toUpperCase(); // error!
elemItr.b.toFixed(); // error!
}
// I expected either this (intersection of element types)
const elemIdx = arr[0]; // { a: string; } & { b: number; }
elemIdx.a.toUpperCase(); // okay
elemIdx.b.toFixed(); // okay
// or this (overloaded iterators giving the first element type only)
const iter = arr[Symbol.iterator];
/* const iter: {
(): IterableIterator<{ a: string }>;
(): IterableIterator<{ a: string }>;
} & {
(): IterableIterator<{ b: number }>;
(): IterableIterator<{ b: number }>;
} */
const result = arr[Symbol.iterator]().next();
if (!result.done) {
result.value.a.toUpperCase(); // okay
result.value.b.toFixed(); // error, expected this
}
Compiler Options
{
"compilerOptions": {
"noImplicitAny": true,
"strictNullChecks": true,
"strictFunctionTypes": true,
"strictPropertyInitialization": true,
"strictBindCallApply": true,
"noImplicitThis": true,
"noImplicitReturns": true,
"useDefineForClassFields": false,
"alwaysStrict": true,
"allowUnreachableCode": false,
"allowUnusedLabels": false,
"downlevelIteration": false,
"noEmitHelpers": false,
"noLib": false,
"noStrictGenericChecks": false,
"noUnusedLocals": false,
"noUnusedParameters": false,
"esModuleInterop": true,
"preserveConstEnums": false,
"removeComments": false,
"skipLibCheck": false,
"checkJs": false,
"allowJs": false,
"declaration": true,
"experimentalDecorators": false,
"emitDecoratorMetadata": false,
"target": "ES2017",
"module": "ESNext"
}
}
Playground Link: Provided
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从提供的 TypeScript Playground 链接开始,精简数组交集示例,以比较 for-of 迭代、索引访问和显式调用 Symbol.iterator。确定 for-of 应产生的元素类型,然后根据报告的编译器输出验证所选行为,并为 reproducer 添加覆盖测试。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- typescript
- 领域
- compilers
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100