summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormax <36980911+pr2502@users.noreply.github.com>2022-06-21 19:44:09 (GMT)
committerGitHub <noreply@github.com>2022-06-21 19:44:09 (GMT)
commitdd5cf84f245abf84405833320b8f25dbc43b24d2 (patch)
tree54d73a5df6936314eaa675beb66eeb0366a0cad3
parent51d673176ac90f2144e3e7a492e5b3ea53bdba2e (diff)
downloadcpython-dd5cf84f245abf84405833320b8f25dbc43b24d2.zip
cpython-dd5cf84f245abf84405833320b8f25dbc43b24d2.tar.gz
cpython-dd5cf84f245abf84405833320b8f25dbc43b24d2.tar.bz2
Tutorial: specify match cases don't fall through (GH-93615)
-rw-r--r--Doc/tutorial/controlflow.rst6
1 files changed, 4 insertions, 2 deletions
diff --git a/Doc/tutorial/controlflow.rst b/Doc/tutorial/controlflow.rst
index f6e013b..99a77e7 100644
--- a/Doc/tutorial/controlflow.rst
+++ b/Doc/tutorial/controlflow.rst
@@ -253,8 +253,10 @@ at a more abstract level. The :keyword:`!pass` is silently ignored::
A :keyword:`match` statement takes an expression and compares its value to successive
patterns given as one or more case blocks. This is superficially
similar to a switch statement in C, Java or JavaScript (and many
-other languages), but it can also extract components (sequence elements or
-object attributes) from the value into variables.
+other languages), but it's more similar to pattern matching in
+languages like Rust or Haskell. Only the first pattern that matches
+gets executed and it can also extract components (sequence elements
+or object attributes) from the value into variables.
The simplest form compares a subject value against one or more literals::