SR-11926: [FileHandle] Ensure the Darwin compatibility of Access Control of new methods. #2585
Conversation
This file contains 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 test |
|
Note that at least some of these changes are incorrect. e.g.: write(contentsOf:) is public, not open, on Darwin. |
|
It seems to come to a conclusion. |
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.
From Swift 5.0, new APIs of
FileHandleare introduced.While they are defined as
openin DarwinFoundation (as you know they are imported from objc), they arepublicin SwiftFoundation.They should be defined as
openalso in SwiftFoundation to ensure compatibility (for example, making subclasses ofFileHandlein other modules).Resolves SR-11926.