`assert_never` fails on match-casing `enum` with only one member

[otaj]

Bug Report

When there is only one member of the enum, mypy doesn't perform full exhaustiveness checking and reaches assert_never statement, although it shouldn't.

To Reproduce

mypy-play link

Expected Behavior

mypy does not complain and reports no errors

Actual Behavior

mypy reaches unreachable code and complains

main.py:15: error: Argument 1 to "assert_never" has incompatible type "A"; expected "NoReturn" [arg-type]

Your Environment

Playground

Rationale

While having an enum with only one member is definitely a contrived example, it is a valid example nonetheless. This popped up for me while I was implementing a feature partially for just one case of an enum first with the plan of filing up more enum cases later on.

Note that this is specific for enums with one member only, if you have a Literal with only one member, mypy correctly deduces that unreachable code is truly unreachable. If you have an enum with multiple members (and an appropriate match-case block), the unreachable code is also correctly deduced.

[athuras]

I also just spent 10-minutes fighting this and thought I was going crazy. Single-item enums are typically intended to eventually have more than one item; so exhaustiveness checks on their use are valid and useful (to keep things in sync).

[jakubbortlik]

This seems to be fixed in version 1.10. I've just tried the example in mypy-play, and it passes just fine.

[superosku]

Fixed here: #16966

Duplicate with: #14109

[ilevkivskyi]

Yes, this is fixed now.