Skip to content

Conversation

@ahoppen
Copy link
Member

@ahoppen ahoppen commented Feb 6, 2025

This is more explicit than using #if canImport(PackageModel).

…iftPM support

This is more explicit than using `#if canImport(PackageModel)`.
@ahoppen
Copy link
Member Author

ahoppen commented Feb 6, 2025

@swift-ci Please test

.enableUpcomingFeature("InternalImportsByDefault"),
.enableUpcomingFeature("MemberImportVisibility"),
]
if noSwiftPMDependency {
Copy link
Contributor

Choose a reason for hiding this comment

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

I was going to ask where this was set, but we apparently had it already 😅. The double negative is a bit weird, but I suppose having SWIFTPM_DEPENDENCY would also be a bit weird, so maybe the double negative is the lesser of two evils.

@ahoppen ahoppen enabled auto-merge February 6, 2025 05:54
@ahoppen ahoppen merged commit 825c17e into swiftlang:main Feb 6, 2025
3 checks passed
@ahoppen ahoppen deleted the active-compilation-condition-no-swiftpm branch August 4, 2025 10:48
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