"Structural pattern matching" for Python, part 2 [LWN.net]

"Structural pattern matching" for Python, part 2

Posted Sep 16, 2020 15:59 UTC (Wed) by HelloWorld (guest, #56129)
In reply to: "Structural pattern matching" for Python, part 2 by udifuchs
Parent article: "Structural pattern matching" for Python, part 2

> case Point2D(x, y):
>
> It looks like the class is being initiated.

No, it doesn't, because there is a case keyword right before it, it's pretty much impossible to miss. If the reader doesn't know what that means and starts making wild guesses, the problem isn't with the language but with the reader.

to post comments

"Structural pattern matching" for Python, part 2

Posted Sep 18, 2020 4:23 UTC (Fri) by udifuchs (guest, #141354) [Link]

I know that a computer parser could easily understand this syntax. Still, as a human, I find it confusing. Most keywords in python are followed by an expression. The case keyword is followed by a pattern that has a syntax similar to an expression. This is confusing.

The PEP mentions that assignment targets in python also look like expressions, but this is true in a very narrow way. It is a syntax error to write 'int(x) = 3', while 'case int(x):' is valid.

More specifically, while reading the is_tuple() example in the PEP, it took me a while to realize that LParen() is initialized in the original code but not in the new code. If LParen.__init__() has some side effects, the two versions of the code that look very similar could be very different.