Skip to content

Cherry-pick Disable check for unsafe flags. (#8896) #8914

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

Open
wants to merge 1 commit into
base: release/6.2
Choose a base branch
from

Conversation

dschaefer2
Copy link
Member

Cherry-pick #8896

As discussed in the Swift forums below, a number of projects require the use of "unsafe" flags. A common example is the use of absolute header include paths set via an environment variable that project consumers agree to use. As such, the flags can be safely used under those circumstances.

This change disables the one line that was doing the check.

We will further study the issue and come up with other mechanisms to ensure the challenges some flags have on quality of the package ecosystem are mitigated.

https://forums.swift.org/t/pitch-disable-checks-for-unsafe-flags-in-swiftpm/80698

As discussed in the Swift forums below, a number of projects require the
use of "unsafe" flags. A common example is the use of absolute header
include paths set via an environment variable that project consumers
agree to use. As such, the flags can be safely used under those
circumstances.

This change disables the one line that was doing the check.

We will further study the issue and come up with other mechanisms to
ensure the challenges some flags have on quality of the package
ecosystem are mitigated.


https://forums.swift.org/t/pitch-disable-checks-for-unsafe-flags-in-swiftpm/80698
@dschaefer2
Copy link
Member Author

@swift-ci please 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.

1 participant