Started a heuristic marker inference tool #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Changed?
This adds a new tool to the arsenal that uses naming heuristics to assign the kinds of markers that our collated policies use.
This is intended to set up the basic infrastructure for a marker assigner consisting of a recursive directory traversal, parsing using
syn
and a few sketch heuristics to begin with. It is intended that the heuristics later expand with more patterns we find in the projects we analyze.Why Does It Need To?
This should make it easier to add markers to new applications for analysis with Paralegal.
The idea is that instead of starting marking for every application form scratch we can instead apply the same rules we used in previous applications to add as many markers as possible automatically.
Checklist
good record of what changed.
if necessary
.github/workflows/rust.yml
) either as compiler test or integration test.Or justification for their omission from CI has been provided in this PR
description.