-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Improve wording of isAdditionalFlow/TaintStep qldoc #8638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve wording of isAdditionalFlow/TaintStep qldoc #8638
Conversation
cpp/ql/lib/semmle/code/cpp/dataflow/internal/tainttracking1/TaintTrackingImpl.qll
Outdated
Show resolved
Hide resolved
* Holds if the additional flow step from `node1` to `node2` must be taken | ||
* into account in the analysis. | ||
* Holds if the analysis should assume that data may flow from `node1` to `node2` | ||
* in addition to the normal dataflow steps. | ||
*/ | ||
predicate isAdditionalFlowStep(Node node1, Node node2) { none() } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a rather long way of phrasing "data may flow from node1
to node2
". Would it be equally clear to just write:
Holds if data may flow from
node1
tonode2
in addition to the normal dataflow steps.
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I believe we tend to write data-flow steps
instead of dataflow steps
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
~400 matches for dataflow
(including spaces, case-sensitive) and ~800 for data-flow
, so I've gone with the majority but we're far from consistent
@jketema @MathiasVP taken both suggestions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
While this is being changed, would it make sense to rename the parameters to something more intuitive/descriptive? |
@jketema please re-approve |
@Marcono1234 at #8616 asked that we avoid using
must
with the possible implication that this is a mandatory "waypoint" / "via" step, rather than an additional step that may or may not be used in a given path.