microsoft / microsoft/TypeScript
new Map() infers type only from the first item in the iterable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
TypeScript Version: 3.8.3
Search Terms: map infer type first item
Code
type Lookup = Map<number, boolean | string>;
const foo = new Map([
[1, true],
[2, 'foo']
]);
const bar: Lookup = new Map([
[1, true],
[2, 'foo']
]);
const baz: Lookup = new Map<number, boolean | string>([
[1, true],
[2, 'foo']
]);
Expected behavior: All 3 assignments work.
Actual behavior: The first 2 assignments fail because the type of the map is inferred as Map<number, () => boolean> (because of the first item). The 3rd one works but duplicates the type of the map.
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 TypeScript 3.8.3 behavior in the linked Playground using the three Map examples. Trace how the checker infers the type of the iterable passed to the Map constructor, then verify that all three assignments accept mixed boolean and string values without requiring a duplicated explicit type.
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
- Clearly specified
- Newbie friendliness
- 38/100