Use the '-define-availability' frontend flag directly in CMake rules #529
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 replaces usages of the
-enable-experimental-feature AvailabilityMacro=X
Swift frontend flag in swift-testing's CMake rules with-define-availability X
.Motivation:
The former flags are used in
Package.swift
as a workaround because SwiftPM does not allow using unsafe flags in package dependencies. But this workaround is not necessary when building with CMake—we can use the-define-availability
flag directly without restriction.Using this workaround when building via CMake with Library Evolution enabled causes every specified availability macro flag to be printed in the textual
.swiftinterface
file for the module. This information is not needed by clients of theTesting
module, so the primary motivation of this change is to remove those unnecessary flags from that interface file.Checklist: