[Backport maintenance/2.15.x] Prevent used-before-assignment in pattern matching with a guard

doc/whatsnew/fragments/5327.false_positive

@@ -0,0 +1,4 @@
+Fix false-positive for ``used-before-assignment`` in pattern matching
+with a guard.
+
+Closes #5327

pylint/checkers/variables.py

@@ -1945,6 +1945,7 @@ def _is_variable_violation(
                             nodes.AugAssign,
                             nodes.Expr,
                             nodes.Return,
+                            nodes.Match,
                         ),
                     )
                     and VariablesChecker._maybe_used_and_assigned_at_once(defstmt)
@@ -2045,6 +2046,8 @@ def _maybe_used_and_assigned_at_once(defstmt: nodes.Statement) -> bool:
         """Check if `defstmt` has the potential to use and assign a name in the
         same statement.
         """
+        if isinstance(defstmt, nodes.Match):
+            return any(case.guard for case in defstmt.cases)
         if isinstance(defstmt.value, nodes.BaseContainer) and defstmt.value.elts:
             # The assignment must happen as part of the first element
             # e.g. "assert (x:= True), x"

tests/functional/u/used/used_before_assignment_py310.py

@@ -0,0 +1,7 @@
+"""Tests for used-before-assignment with python 3.10's pattern matching"""
+
+match ("example", "one"):
+    case (x, y) if x == "example":
+        print("x used to cause used-before-assignment!")
+    case _:
+        print("good thing it doesn't now!")

tests/functional/u/used/used_before_assignment_py310.rc

@@ -0,0 +1,2 @@
+[testoptions]
+min_pyver=3.10