[Sema] Revert enabling require-explicit-availability for public modules by default #61161
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
|
@swift-ci Please smoke test |
tshortli
approved these changes
Sep 16, 2022
|
The macOS failure is unrelated: |
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 is a partial revert of #61105. Passing the flag
-require-explicit-availability=ignoreto the stdlib broke the bot building the stdlib with the last toolchain. We should wait until the flag is available in a toolchain on swift.org before we adopt it in the stdlib. Until we can use the flag, to avoid misleading warnings in the stdlib I'm also reverting the automatic enabling of require-explicit-availability for public modules.rdar://99993044