Skip to content

Conversation

@compnerd
Copy link
Member

The FileHandle extension added an overloaded close that causes
ambiguity when using close on a FileHandle. This manifested as a
build failure with swiftlang/swift-package-manager#3888. Remove the
function as swift-driver, swift-package-manager, and sourcekit-lsp are
able to build without this function (relying on Foundation to provide
it).

The `FileHandle` extension added an overloaded `close` that causes
ambiguity when using `close` on a `FileHandle`.  This manifested as a
build failure with swiftlang/swift-package-manager#3888.  Remove the
function as swift-driver, swift-package-manager, and sourcekit-lsp are
able to build without this function (relying on Foundation to provide
it).
@compnerd
Copy link
Member Author

@swift-ci please test

@compnerd
Copy link
Member Author

CC: @abertelrud

@abertelrud
Copy link
Contributor

I just realized what happened here. These were old covers that are no longer needed now that Foundation has refined its FileHandle API in Swift 5.0.

This was swiftlang/swift-corelibs-foundation@55c404b

@abertelrud
Copy link
Contributor

That means that if this causes problems, I can also switch SwiftPM to use the deprecated closeFile() call. But fixing forward is better.

@abertelrud
Copy link
Contributor

@compnerd Looks ready to go at this point?

@compnerd compnerd merged commit 6c8bcd6 into swiftlang:main Dec 1, 2021
@compnerd compnerd deleted the closed branch December 1, 2021 02:01
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.

2 participants