Skip to content

Commit 59b26c0

Browse files
authored
Update docs/codeql/codeql-language-guides/advanced-dataflow-scenarios-cpp.rst
1 parent b71248f commit 59b26c0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/codeql/codeql-language-guides/advanced-dataflow-scenarios-cpp.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ However, when a write to a field is not visible to CodeQL (for example, because
1818

1919
When you write additional flow steps to track pointers, you must decide whether the dataflow step should flow from the pointer or its indirection. Similarly, you must decide whether the additional step should target a pointer or its indirection.
2020

21-
In the dual situation where a read of a field is not visible to CodeQL, the dataflow library's "implicit read" mechanism can be used to achieve the right flow.
21+
In contrast, if the read of a field is not visible to CodeQL, you can add an ``allowImplicitRead`` predicate to model the data flow.
2222

2323
The setup
2424
---------

0 commit comments

Comments
 (0)