Skip to content

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

Merged
merged 1 commit into from
May 1, 2023

Conversation

compnerd
Copy link
Member

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.

@compnerd
Copy link
Member Author

@swift-ci please smoke test

Copy link
Contributor

@MaxDesiatov MaxDesiatov left a 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!

@compnerd
Copy link
Member Author

@swift-ci please smoke test

@compnerd
Copy link
Member Author

@swift-ci please smoke test

@compnerd
Copy link
Member Author

@swift-ci please smoke test

@compnerd
Copy link
Member Author

@swift-ci please test Windows platform

@compnerd
Copy link
Member Author

@swift-ci please smoke test

Copy link
Contributor

@tomerd tomerd left a 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

@compnerd compnerd force-pushed the aboriginal branch 2 times, most recently from de6a4a4 to bbf6b76 Compare May 1, 2023 16:50
@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

@swift-ci please test

@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

@swift-ci please smoke test

@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

Okay, tested locally on Windows and macOS, I think that this should be good on both finally!

@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

@swift-ci please smoke test

@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

@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.
@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

@swift-ci please test

@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

@swift-ci please smoke test

@compnerd
Copy link
Member Author

compnerd commented May 1, 2023

@swift-ci please test

Copy link
Contributor

@tomerd tomerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @compnerd

@tomerd tomerd enabled auto-merge (squash) May 1, 2023 17:48
@tomerd tomerd merged commit 97e099b into swiftlang:main May 1, 2023
@compnerd compnerd deleted the aboriginal branch May 1, 2023 20:26
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.

4 participants