Tagging typically depends on DFG and also on EOG

[KuechA]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.27%. Comparing base (81f7971) to head (c432a54).
⚠️ Report is 10 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Files with missing lines	Coverage Δ
...hofer/aisec/cpg/passes/concepts/TagOverlaysPass.kt	80.00% <ø> (ø)

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[oxisto]

SymbolResolver should already depend on EOG, so does CF-DFG and/or PointsToPass. Why is this even necessary?

[KuechA]

For CF-DFG and PointsToPass: These are optional, so if we do not register them, it means that only the SymbolResolver is left. I saw this pass being executed before the DFG Pass which was strange. And I prefer to have such dependencies/assumptions written down explicitly. But I agree, the EOG may not be strictly necessary here.