parent
771b2a8db0
commit
29ddc84b4d
|
@ -30,7 +30,7 @@ both static and runtime specifications.
|
|||
were rejected. Instead of targeting the optimization of
|
||||
``if ... elif ... else`` statements (as those PEPs did), this design
|
||||
focuses on generalizing sequence, mapping, and object destructuring.
|
||||
It uses sytactic features made possible by :pep:`617`, which
|
||||
It uses syntactic features made possible by :pep:`617`, which
|
||||
introduced a more powerful method of parsing Python source code.
|
||||
|
||||
|
||||
|
@ -67,7 +67,7 @@ This is in contrast with the opposite sides of both aspects:
|
|||
|
||||
This PEP aims at improving the support for destructuring heterogeneous data
|
||||
by adding a dedicated syntactic support for it in the form of pattern matching.
|
||||
On very high level it is similar to regular expressions, but instead of
|
||||
On a very high level it is similar to regular expressions, but instead of
|
||||
matching strings, it will be possible to match arbitrary Python objects.
|
||||
|
||||
We believe this will improve both readability and reliability of relevant code.
|
||||
|
|
Loading…
Reference in New Issue