Mapped types intersections are too eagerly resolved

TypeScript Version: nightly (2.5.0-dev.20170727)

Code

type StringContains<S extends string, L extends string> = (
    { [K in S]:      'true' } &
    { [key: string]: 'false' }
  )[L]

type ObjectHasKey<O, L extends string> = StringContains<keyof O, L>

type First<T> = ObjectHasKey<T, '0'> // eagerly resolved as 'false'

Expected behavior:
Type First should be left as an indexing operation.

PS: origin of the issue: gcanti/typelevel-ts#8

Anders Hejlsberg (@ahejlsberg)

Anders Hejlsberg (@ahejlsberg) Could you have a look at this one too?

Navigation Menu

Repository navigation

Mapped types intersections are too eagerly resolved #17456

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Mapped types intersections are too eagerly resolved #17456

Description

Activity

SimonMeskens commented on Jul 27, 2017

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions