Skip to content

[stable/20250402][clang][Dependency Scanning] Report What a Module Exports during Scanning (#137421) #10670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 12, 2025

Conversation

bnbarham
Copy link

We would like to report, for a module, which direct dependencies it exports during dependency scanning. This PR implements this reporting by augmenting ModuleDep's ClangModuleDeps variable. ClangModuleDeps now contains instances of DepInfo, which is made of a ModuleID and a boolean flag that indicates if a particular dependence is exported.

rdar://144794793
(cherry picked from commit ea1bfbf)

…ning (llvm#137421)

We would like to report, for a module, which direct dependencies it
exports during dependency scanning. This PR implements this reporting by
augmenting `ModuleDep`'s `ClangModuleDeps` variable. `ClangModuleDeps`
now contains instances of `DepInfo`, which is made of a `ModuleID` and a
boolean flag that indicates if a particular dependence is exported.

rdar://144794793
(cherry picked from commit ea1bfbf)
@bnbarham bnbarham merged commit 0714626 into swiftlang:stable/20250402 May 12, 2025
@bnbarham bnbarham deleted the cherry-missing-scan branch May 12, 2025 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants