I think we are storing up trouble unless we 1) Allow arbitrary expressions after `case`, interpreted *as now* 2) Use *different* syntaxes, not legal in expressions, for alternative matching values (i.e. not `|` or `or`) (NB simply stacking with multiple `case` lines is one possibility) templates such as `Point(x, 0)` anything else particular to `match` I am reminded of the special restrictions for decorator syntax, which were eventually removed. On 24/06/2020 20:38, Guido van Rossum wrote:
Everyone,
If you've commented and you're worried you haven't been heard, please add your issue *concisely* to this new thread. Note that the following issues are already open and will be responded to separately; please don't bother commenting on these until we've done so:
- Alternative spellings for '|' - Whether to add an 'else' clause (and how to indent it) - A different token for wildcards instead of '_' - What to do about the footgun of 'case foo' vs. 'case .foo'
(Note that the last two could be combined, e.g. '?foo' or 'foo?' to mark a variable binding and '?' for a wildcard.)
-- --Guido van Rossum (python.org/~guido <http://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-c...>
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/STJSSAET... Code of Conduct: http://python.org/psf/codeofconduct/