It means "I can't prove it matches". This should be clear from the spec already (it's an important point actually, since it means type checkers cannot narrow in an else clause). So please don't file a PR to "add" this.
On Thu, Feb 11, 2021 at 11:49 AM Jim J. Jewett <[email protected]> wrote: > If a TypeGuard returns false, does that mean "it doesn't match", or just > "I can't prove it matches, but it still might"? That seems relevant to the > else clause ... and seems to have changed since the last version I looked > at. > > -jJ > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/KCJ2IIF4BUXGQEBLBPFNKPXZCGUHVIPD/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/5YP4NEEBV3NOHQZMDRTP5DV4DWWAYVFC/ Code of Conduct: http://python.org/psf/codeofconduct/
