Repository navigation
Exhaustive tuple match reports a missing return #5621
Description
Describe the Bug
def without_fallback(left: bool, right: bool) -> int:
match left, right:
case True, True: return 0
case True, False: return 1
case False, True: return 2
case False, False: return 3
def with_fallback(left: bool, right: bool) -> int:
match left, right:
case True, True: return 0
case True, False: return 1
case False, True: return 2
case False, False: return 3
case remaining:
assert_never(remaining)without_fallback gives:
ERROR Function declared to return `int`, but one or more paths are missing an explicit `return` [bad-return]
I'd expect both functions to be accepted, as the four cases cover every combination of the two booleans. The accepted assert_never suggests Pyrefly already knows that no values can reach the final case 🤔
Sandbox Link
(Only applicable for extension issues) IDE Information
No response
Activity
rchen152 commentedon Nov 13, 2026
Thanks for the report! This looks like it likely has the same cause as #5206, so I'm going to merge them.