-
Notifications
You must be signed in to change notification settings - Fork 204
[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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was in-place as a temporary shim while SwiftPM adapted the `InterModuleDependencyOracle` API and a lighter-weight `ExternalTargetModulePathMap`.
@swift-ci please test |
This was referenced Jul 7, 2021
Cross-repo tests from the Swift and SwiftPM repositories are all green. |
nkcsgexi
approved these changes
Jul 8, 2021
There was a problem hiding this 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!
@swift-ci please test |
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was in-place as a temporary shim while SwiftPM adapted the
InterModuleDependencyOracle
API and a lighter-weightExternalTargetModulePathMap
.