Skip to content

Conversation

@cachemeifyoucan
Copy link
Contributor

If a testable module is loaded from a non-testable import, ignore its optional dependencies because the consumer should not use them. This matches the behavior of the implicit build or the behavior how forwarding module is created.

@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

@cachemeifyoucan cachemeifyoucan force-pushed the eng/PR-testable-import-deps-optional branch from abddb06 to 70762fa Compare April 17, 2024 19:44
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

@cachemeifyoucan
Copy link
Contributor Author

@artemcm this tries to fix the binary testable module in a different direction to match better with the current behavior.

Copy link
Contributor

@artemcm artemcm left a comment

Choose a reason for hiding this comment

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

Makes sense. Thanks.

@cachemeifyoucan cachemeifyoucan force-pushed the eng/PR-testable-import-deps-optional branch from 70762fa to eb5981b Compare April 18, 2024 00:01
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

1 similar comment
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

If a testable module is loaded from a non-testable import, ignore its
optional dependencies because the consumer should not use them. This
matches the behavior of the implicit build or the behavior how
forwarding module is created.
@cachemeifyoucan cachemeifyoucan force-pushed the eng/PR-testable-import-deps-optional branch from eb5981b to 77fefe9 Compare April 18, 2024 02:11
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

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