Skip to content

Commit 404b0f2

Browse files
committed
JS: Fix another stray reference to BarrierGuardNode/SanitizerGuardNode
1 parent 422c089 commit 404b0f2

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

docs/codeql/codeql-language-guides/using-flow-labels-for-precise-data-flow-analysis.rst

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -126,8 +126,7 @@ introduced any sanitizers yet.
126126

127127
There are many ways of checking for nullness directly or indirectly. Since this is not the main
128128
focus of this tutorial, we will only show how to model one specific case: if some variable ``v`` is
129-
known to be truthy, it cannot be ``null``. This kind of condition is easily expressed using a
130-
``BarrierGuardNode`` (or its counterpart ``SanitizerGuardNode`` for taint-tracking configurations).
129+
known to be truthy, it cannot be ``null``. This kind of condition is expressed using a "barrier guard".
131130
A barrier guard node is a data-flow node ``b`` that blocks flow through some other node ``nd``,
132131
provided that some condition checked at ``b`` is known to hold, that is, evaluate to a truthy value.
133132

0 commit comments

Comments
 (0)