Skip to content

C/C++: Skip redundant iterator use-use edges. - #23018

Open
aschackmull wants to merge 1 commit into
github:mainfrom
aschackmull:cpp/iterator-use-use
Open

aschackmull wants to merge 1 commit into
github:mainfrom
aschackmull:cpp/iterator-use-use

Conversation

@aschackmull

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions github-actions Bot added the C++ label Nov 4, 2026
@aschackmull

Copy link
Copy Markdown
Contributor Author

Dca is uneventful.

@aschackmull
aschackmull marked this pull request as ready for review November 5, 2026 08:49
@aschackmull
aschackmull requested a review from a team as a code owner November 5, 2026 08:49
Copilot AI auto review requested due to automatic review settings November 5, 2026 08:49

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for the change excluding redundant iterator use-use edges from C/C++ IR data flow.

No open issues 🎉

What changed in this PR

This PR removes redundant iterator use-use edges from C/C++ IR data flow, relying on regular SSA flow to handle those connections and respect modeled flow barriers.

Changes:

  • Passes false to exclude use-use steps from iterator local flow.
  • Adds a comment explaining why regular SSA flow already covers these steps.
File Description
cpp/​ql/​lib/​semmle/​code/​cpp/​ir/​dataflow/​internal/​DataFlowPrivate.qll Excludes redundant iterator use-use steps and documents the rationale.

Review effort: Balanced (auto)

@aschackmull aschackmull added the no-change-note-required This PR does not need a change note label Nov 5, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C++ no-change-note-required This PR does not need a change note

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants