镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Intersection with mapped never type allows incompatible optional assignments #19927

Description

TypeScript Version: 2.7.0-dev.20171110

Code

declare const a:  {z: string} & {[K in never]: string} 
const b: {z?: number} = a

Expected behavior:
Compile error on the second line because {z?: number} is incompatible with {z: string}

Actual behavior:
No Error

Obviously the code above is nonsensical but I spun this out of a special case in #19869 since that one ended up being about generic function inferences and I realized this is something different.

Some more code examples that make me think my example should have a compile error:

declare const a2: {z: string} & {[K in never]: string}
const b2: {z: number} = a2 
// TS2322: Type '{ z: string; } & {}' is not assignable to type '{ z: number; }'.

declare const a3: {z: string} & {}
const b3: {z?: number} = a3 
// TS2322: Type '{ z: string; }' is not assignable to type '{ z?: number | undefined; }'.

declare const a4: {z: string, y: string} & {[K in never]: string}
const b4: {z?: number, y: string} = a4 
// TS2322: Type '{ z: string; y: string; } & {}' is not assignable to type '{ z?: number | undefined; y: string; }'.

Activity

  1. jcalz commented on Nov 25, 2022

    @jcalz
    Contributor

    Looks like this has been fixed as of TS3.9

  2. jakebailey commented on Jul 9, 2023

    @jakebailey
    Member

    Just looking at old issues; this was fixed in #37195 (so, 3.9, as noted above).

  3. locked as resolved and limited conversation to collaborators on Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA bug in TypeScript

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions