-
Notifications
You must be signed in to change notification settings - Fork 15
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
Replace custom async
file system wrapper with NIOFileSystem
#76
Comments
Hi, I was wondering if I could work on this? As I was poking around I noticed that running
Also this is my first time using
|
Yes, as this is an issue marked as "good first issue" and is unassigned, it's free for anyone for anyone to work on. Feel free to fix soundness and formatting issues, but those should be submitted as separate PRs so that those changes don't pollute other PRs one may submit as part of their work. |
This will effectively prevent porting to windows until NIO properly supports windows. I would prefer that we didn't do this. |
It won't change the status quo WRT Window support, as Swift SDK Generator already depends on SwiftNIO. |
Ah, that's rather unfortunate. |
Could the new Foundation help with the NIO dependency? Though it doesn't look like SubProcess has made it in yet. |
No, it won't help since relevant Foundation APIs are not |
Motivation: Add support for _NIOFileSystem to move away from OSFileSystem as per issue swiftlang#76. Modifications: Add SDKFileSystem that uses _NIOFileSystem. Change default AsyncFileSystem to SDKFileSystem Result: Using Swift NIO for file system operations.
We currently have our own, not necessarily well-tested or valid implementation of
async
file system APIs in https://github.com/apple/swift-sdk-generator/tree/main/Sources/GeneratorEngine/FileSystem. WithNIOFileSystem
now available in SwiftNIO 2.63, we should use that instead.The text was updated successfully, but these errors were encountered: