typePreservingStep
This requires a bit of explanation, so strap in. Firstly, because we use `LocalSourceNode`s as the start and end points of our `StepSummary::step` relation, there's no need to include `simpleLocalFlowStep` (via `typePreservingStep`) in `smallstep`. Indeed, since the successor node for a `step` is a `LocalSourceNode`, and local sources never have incoming flow, this is entirely futile -- we can find values for `mid` and `nodeTo` that satisfy the body of `step`, but `nodeTo` will never be a `LocalSourceNode`. With this in mind, we can simplify `smallstep` to only refer to `jumpStep`. This then brings the other uses of `typePreservingStep` into question. The only other place we use this predicate is in the `TypeTracker` and `TypeBackTracker` `smallstep` predicates. Note, however, that here we no longer need `jumpStep` to be part of `typeTrackingStep` (as it is already accounted for in `StepSummary::smallstep`) so we can simplify to `simpleLocalFlowStep`. At this point, `typePreservingStep` is unused. Finally, because of the way `smallstep` is used in `step` (inside `StepSummary`), `nodeTo` must always be a `LocalSourceNode`, so I have propagated this restriction to `smallstep` as well. We can always lift this restriction later, but for now it seems like it's likely to cause fewer surprises to have made this explicit.
CodeQL
This open source repository contains the standard CodeQL libraries and queries that power LGTM and the other CodeQL products that GitHub makes available to its customers worldwide. For the queries, libraries, and extractor that power Go analysis, visit the CodeQL for Go repository.
How do I learn CodeQL and run queries?
There is extensive documentation on getting started with writing CodeQL. You can use the interactive query console on LGTM.com or the CodeQL for Visual Studio Code extension to try out your queries on any open source project that's currently being analyzed.
Contributing
We welcome contributions to our standard library and standard checks. Do you have an idea for a new check, or how to improve an existing query? Then please go ahead and open a pull request! Before you do, though, please take the time to read our contributing guidelines. You can also consult our style guides to learn how to format your code for consistency and clarity, how to write query metadata, and how to write query help documentation for your query.
License
The code in this repository is licensed under the MIT License by GitHub.
Visual Studio Code integration
If you use Visual Studio Code to work in this repository, there are a few integration features to make development easier.
CodeQL for Visual Studio Code
You can install the CodeQL for Visual Studio Code extension to get syntax highlighting, IntelliSense, and code navigation for the QL language, as well as unit test support for testing CodeQL libraries and queries.
Tasks
The .vscode/tasks.json file defines custom tasks specific to working in this repository. To invoke one of these tasks, select the Terminal | Run Task... menu option, and then select the desired task from the dropdown. You can also invoke the Tasks: Run Task command from the command palette.