I noticed this issue while updating the typing conformance tests. On this code snippet, which is taken from the tuples_type_compat conformance test, pyright 1.1.407 behaves correctly (errors on exactly one assert_type in each match case, showing that it infers one of the two acceptable types in each case), whereas pyright 1.1.408 incorrectly marks the code in the last match case as unreachable.
I noticed this issue while updating the typing conformance tests. On this code snippet, which is taken from the tuples_type_compat conformance test, pyright 1.1.407 behaves correctly (errors on exactly one
assert_typein eachmatchcase, showing that it infers one of the two acceptable types in each case), whereas pyright 1.1.408 incorrectly marks the code in the last match case as unreachable.