Translate Python CodeQL DIL rules to Ascent - #1
Merged
Conversation
StarGazerM
marked this pull request as ready for review
July 29, 2026 07:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Why
The previous Python implementation mixed numeric extractor encodings, raw Rust plumbing, and approximate query logic. That prevented a line-by-line mapping back to compiled CodeQL DIL and made semantic parity difficult to audit.
Current status
This PR does not claim complete Cyclic Import or full Python CodeQL parity. The canonical
points_toclosure and the recursiveAbsentModuleandBoundMethodportions still need direct DIL translation. The incomplete query therefore remains outside the provider registry.Validation
cargo test -p codeql-ascent-pythoncargo check -p codeql-ascent-python --all-targetscargo fmt --all -- --checkgit diff --check