-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Basics: introduce some native path representation helpers #6454
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
Conversation
@swift-ci please smoke test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me, just a small nit to make import statements more consistent. Thanks!
@swift-ci please smoke test |
@swift-ci please smoke test |
@swift-ci please smoke test |
@swift-ci please test Windows platform |
@swift-ci please smoke test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, had some late realization about the String level API, but once that is addressed we should be good
de6a4a4
to
bbf6b76
Compare
@swift-ci please test |
@swift-ci please smoke test |
Okay, tested locally on Windows and macOS, I think that this should be good on both finally! |
@swift-ci please smoke test |
@swift-ci please test |
We end up needing these in a few places, and while we could make it `internal` and use `@testable` imports in the tests, this ends up being needed in `Build` and `PackageLoading`. Ideally, we would give it package visibility, but that functionality would not be backwards compatible. This is a reluctant approach at solving that problem by using `public` visibility.
@swift-ci please test |
@swift-ci please smoke test |
@swift-ci please test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @compnerd
We end up needing these in a few places, and while we could make it
internal
and use@testable
imports in the tests, this ends up being needed inBuild
andPackageLoading
. Ideally, we would give it package visibility, but that functionality would not be backwards compatible. This is a reluctant approach at solving that problem by usingpublic
visibility.