Skip to content

[Gardening] Delete deprecated API for tracking external target information. #749

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
Jul 12, 2021

Conversation

artemcm
Copy link
Contributor

@artemcm artemcm commented Jul 7, 2021

This was in-place as a temporary shim while SwiftPM adapted the InterModuleDependencyOracle API and a lighter-weight ExternalTargetModulePathMap.

This was in-place as a temporary shim while SwiftPM adapted the `InterModuleDependencyOracle` API and a lighter-weight `ExternalTargetModulePathMap`.
@artemcm
Copy link
Contributor Author

artemcm commented Jul 7, 2021

@swift-ci please test

@artemcm
Copy link
Contributor Author

artemcm commented Jul 8, 2021

Cross-repo tests from the Swift and SwiftPM repositories are all green.

@artemcm artemcm requested a review from nkcsgexi July 8, 2021 15:53
Copy link
Contributor

@nkcsgexi nkcsgexi left a comment

Choose a reason for hiding this comment

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

Removing code is always exciting, Thank you!

@artemcm
Copy link
Contributor Author

artemcm commented Jul 12, 2021

@swift-ci please test

@artemcm artemcm merged commit 80fc8e1 into swiftlang:main Jul 12, 2021
artemcm added a commit to artemcm/swift-driver that referenced this pull request Jul 15, 2021
…o the scanning action.

I got overzealous when deleting code in swiftlang#749 and removed one piece of functionality that we still rely on.
Although the external target map is no longer necessary when scanning dependencies using libSwiftScan, we still use it for resolution of `canImport` statements during the scan.
We need to figure out a better way to deal with that in the scanner, but in the meantime this will restore functionality.
artemcm added a commit to artemcm/swift-driver that referenced this pull request Jul 15, 2021
…o the scanning action.

I got overzealous when deleting code in swiftlang#749 and removed one piece of functionality that we still rely on.
Although the external target map is no longer necessary when scanning dependencies using libSwiftScan, we still use it for resolution of `canImport` statements during the scan.
We need to figure out a better way to deal with that in the scanner, but in the meantime this will restore functionality.
artemcm added a commit to artemcm/swift-driver that referenced this pull request Jul 15, 2021
…o the scanning action.

I got overzealous when deleting code in swiftlang#749 and removed one piece of functionality that we still rely on.
Although the external target map is no longer necessary when scanning dependencies using libSwiftScan, we still use it for resolution of `canImport` statements during the scan.
We need to figure out a better way to deal with that in the scanner, but in the meantime this will restore functionality.
artemcm added a commit to artemcm/swift-driver that referenced this pull request Jul 15, 2021
…o the scanning action.

I got overzealous when deleting code in swiftlang#749 and removed one piece of functionality that we still rely on.
Although the external target map is no longer necessary when scanning dependencies using libSwiftScan, we still use it for resolution of `canImport` statements during the scan.
We need to figure out a better way to deal with that in the scanner, but in the meantime this will restore functionality.
artemcm added a commit to artemcm/swift-driver that referenced this pull request Jul 30, 2021
…o the scanning action.

I got overzealous when deleting code in swiftlang#749 and removed one piece of functionality that we still rely on.
Although the external target map is no longer necessary when scanning dependencies using libSwiftScan, we still use it for resolution of `canImport` statements during the scan.
We need to figure out a better way to deal with that in the scanner, but in the meantime this will restore functionality.
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