Enable experimental 'AllowUnsafeAttribute' feature to continue supporting 6.1 development snapshot toolchains #1084
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
…ting 6.1 development snapshot toolchains
stmontgomery
added
bug
stmontgomery
requested review from
grynspan,
briancroom,
SeanROlszewski and
suzannaratcliff
as code owners
|
@swift-ci please test |
briancroom
approved these changes
Apr 18, 2025
suzannaratcliff
approved these changes
Apr 18, 2025
|
@swift-ci please test macOS |
|
The macOS CI failure is expected to be resolved by swiftlang/swift#80830. |
Merged
2 tasks
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 fixes a build failure when attempting to build the
mainbranch using a 6.1 development snapshot toolchain. This failure was introduced by #1069, which added usage of the new@unsafeattribute, and the failure was revealed when we set up the 6.1 CI jobs in #1083.Here are some relevant related Swift PRs which give context around these changes:
@unsafeand the ability to prohibit use of unsafe entities swift#75413See the code comment for more details.
Checklist: