Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Dependency Scanning] Break out Swift Overlay dependencies into separate output category #66031

Merged
merged 1 commit into from
May 23, 2023
Merged

[Dependency Scanning] Break out Swift Overlay dependencies into separate output category #66031

merged 1 commit into from
May 23, 2023

Commits on May 19, 2023

  1. [Dependency Scanning] Break out Swift overlay dependencies into separ… 

    …ate output category

Instead of being a part of 'directDependencies' on a module dependency info, make them a separate array of dependency IDs for Swift Source and Textual modules.

This will allow clients to still distinguish direct module dependencies imported from a given module, versus dependencies added because direct/transitive Clang module dependencies have Swift overlays.

This change does *not* remove overlay dependencies from 'directDependencies' yet, just adds them as a separate field on the module details info. A followup change will remove overlay and bridging header dependencies from 'directDependencies' once the clients have had a chance to adopt to this change.
    @artemcm
    artemcm committed May 19, 2023
    Configuration menu
    Copy the full SHA
    5ca9178 View commit details
    Browse the repository at this point in the history