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

enum exhaustiveness checking with --noImplicitReturns doesn't work for nested switches #27388

Description

TypeScript Version: 3.2.0-dev.20180927

Search Terms:

enum nested switch

Code

enum E {
  A = 'A', B = 'B', C = 'C'
};

function one(e: E): number {
  switch (e) {
    case E.A: return 1;
    case E.B: return 2;
    case E.C: return 3;
  }
}

function two(e: E, f: E): number {
  switch (e) {
  case E.A: return 1;
  case E.B: return 2;
  case E.C:
    switch (f!) {
    case E.A: return 31;
    case E.B: return 32;
    case E.C: return 33;
    }
  }
}

Expected behavior:

Successful compilation: if one is OK, then so is two.

Actual behavior:

flutterby:tmp ariels$ tsc --noImplicitReturns x.ts
x.ts:13:27 - error TS7030: Not all code paths return a value.

13 function two(e: E, f: E): number {

Playground Link:
https://www.typescriptlang.org/play/#src=enum%20E%20%7B%0D%0A%20%20A%20%3D%20'A'%2C%20B%20%3D%20'B'%2C%20C%20%3D%20'C'%0D%0A%7D%3B%0D%0A%0D%0Afunction%20one(e%3A%20E)%3A%20number%20%7B%0D%0A%20%20switch%20(e)%20%7B%0D%0A%20%20%20%20case%20E.A%3A%20return%201%3B%0D%0A%20%20%20%20case%20E.B%3A%20return%202%3B%0D%0A%20%20%20%20case%20E.C%3A%20return%203%3B%0D%0A%20%20%7D%0D%0A%7D%0D%0A%0D%0Afunction%20two(e%3A%20E%2C%20f%3A%20E)%3A%20number%20%7B%0D%0A%20%20switch%20(e)%20%7B%0D%0A%20%20%20%20case%20E.A%3A%20return%201%3B%0D%0A%20%20%20%20case%20E.B%3A%20return%202%3B%0D%0A%20%20%20%20case%20E.C%3A%0D%0A%20%20%20%20%20%20switch%20(f!)%20%7B%0D%0A%20%20%20%20%20%20%20%20case%20E.A%3A%20return%2031%3B%0D%0A%20%20%20%20%20%20%20%20case%20E.B%3A%20return%2032%3B%0D%0A%20%20%20%20%20%20%20%20case%20E.C%3A%20return%2033%3B%0D%0A%20%20%20%20%20%20%7D%0D%0A%20%20%20%20%7D%0D%0A%20%20%7D%0D%0A%7D%0D%0A

Related Issues:

Possibly a simpler case of #23572

Activity

  1. mattmccutchen commented on Sep 27, 2018

    @mattmccutchen
    Contributor

    Possible duplicate of #11572.

  2. ghost added
    DuplicateAn existing issue was already created
    on Sep 27, 2018
  3. typescript-bot commented on Dec 14, 2018

    @typescript-bot
    Contributor

    This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

  4. 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

    DuplicateAn existing issue was already created

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions