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
[SR-1005] SwiftPM port to Foundation #5308
Comments
Here's some of the work I think is involved here:
Between source changes and updates to the build system, I'd hesitate to recommend this as a "StarterBug" – but your bar may be set higher than mine. |
I classified it as Starter as it doesn't require a large understanding of the SwiftPM codebase to work on it. Anyway, I'd like to see Foundation only used as a transitive dependency, I want to keep our high quality due to low optionality and mutable state low. Mainly I see it being important for avoiding the edge-case plague of file system handling etc. |
Being a StarterBug, I've made an attempt at a partial implementation. See #284 |
I have posted my thoughts on what our direction should be here to: |
After seeing the impact of some of these changes, I think now the direction we want is to use Foundation for specific APIs where appropriate, versus just a general port. Closing this out, and we can consider changes on a case by case basis. |
Additional Detail from JIRA
md5: 4a38caa7b18a7e84315c664caa4922f4
relates to:
Path.relative(to:)
solidIssue Description:
SwiftPM was started before Foundation on Linux was mature enough for use, but this is no longer the case.
Port SwiftPM to Foundation and remove the
POSIX
module.However we would prefer to keep a functional approach for eg. NSTask, so add wrappers to
Utility
.The text was updated successfully, but these errors were encountered: