Taine Zhao

@dmoisset I'm glad to see you are taking this feature into consideration, however it seems that your proposed design breaks a feeling that "destructuring should look like an inverse of...

@SaschaSchlemmer This is clean but a bit verbose, especially when the patterns are nested. Also, in your proposal way, I wonder if we're supposed to mark it `global` in each...

@gvanrossum I wonder if using prefix `!` operator to indicate `Store` is rejected? I don't see a discussion about this at here or in the python-dev mailing list. Instead of...

They're both ugly but `!` has a closer meaning for storing variables: https://github.com/gvanrossum/patma/issues/92#issuecomment-649392775

> Which other languages (other than Perl :-) use a marker for stores, and which don't? What do the latter do for loads? In all the languages referenced in your...

> Do those languages that use the case of the first letter in cases also use the case of the first letter in other contexts? I'm not sure what you...

> I meant outside the whole pattern matching part of the language. (E.g. IIRC there are languages that require class names to start with a capital letter.) In fact, a...

Glad to see the authors voting for no uppercase. Many including me believe using uppercases this way is bad for Python. > If it's accepted, I'd solve one minor issue...

TL;DR: No, a global variable `C` is volatile. > The various competing proposals for custom matching do allow this sort of optimization because they are more restricted, which means that...

Doing so is awesome, but as a user often working with `ast` module, I hope we could avoid matching AST types with positional arguments. I cannot always recall the indices...