<!-- If you're not sure whether what you're experiencing is a mypy bug, please see the "Question and Help" form instead. Please consider: - checking our common issues page: https://mypy.readthedocs.io/en/stable/common_issues.html - searching our issue tracker: https://github.com/python/mypy/issues to see if it's already been reported - asking on gitter chat: https://gitter.im/python/typing --> **Bug Report** <!-- If you're reporting a problem with a specific library function, the typeshed tracker is better suited for this report: https://github.com/python/typeshed/issues If the project you encountered the issue in is open source, please provide a link to the project. --> On match case of tuples like `match foo, bar:` you can use case `_, _:` as default, but this is not working as a default for possibly-undefined error. if you use case `_:` as default, is working fine. **To Reproduce** https://gist.github.com/mypy-play/2285fdbaf9db6bfc1245c29f5cd6ca3f **Expected Behavior** The gist should not raise possibly undefined <!-- How did you expect mypy to behave? It’s fine if you’re not sure your understanding is correct. Write down what you thought would happen. If you expected no errors, delete this section. --> **Actual Behavior** it raises possibly undefined. <!-- What went wrong? Paste mypy's output. --> **Your Environment** <!-- Include as many relevant details about the environment you experienced the bug in --> tested on mypy playground as is in the gist. <!-- You can freely edit this text, please remove all the lines you believe are unnecessary. --> note: on pyright works fine: https://pyright-play.net/?code=JYWwDg9gTgLgBDAnmYA7A5gKAGYQgLjjXgF44BGTAIwEMpDi4zLMQaYBjACzlwgBo4tepjhi4HGgGcApnAAMg%2BflHi1VJnABiNADazVYybLgB9QaZVr1ZACpQArjMPXMSFBgB0UGQDcZeqbuMgAUVACUQA
Activity