-
Notifications
You must be signed in to change notification settings - Fork 125
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
TSCBasic: handle empty paths in WindowsPath(validatingRelativePath:)
#403
Conversation
We may not invoke `fileSystemRepresentation` on an empty string as per the API contract for the function. Add guards to prevent that. In order to make this behaviour consistency more visible, reorder the constructors to collate the absolute path and relative path handling.
@swift-ci please test |
@swift-ci please test |
@swift-ci please test macOS platform |
AFAIU macOS job is going to fail until macOS CI nodes are updated to a later version of Xcode that supports Swift 5.7. cc @shahmishal |
macOS Failure:
|
Yeah, that comment looks consistent with the macOS build failure. |
@swift-ci please test Windows platform |
@swift-ci please test macOS platform |
CC: @shahmishal:
|
@swift-ci please test Windows platform |
@swift-ci please test macOS platform |
@swift-ci please test Windows platform |
@swift-ci please test macOS platfom |
@swift-ci please test macOS platform |
3 similar comments
@swift-ci please test macOS platform |
@swift-ci please test macOS platform |
@swift-ci please test macOS platform |
@swift-ci test macos |
1 similar comment
@swift-ci test macos |
@swift-ci please test macOS platform |
1 similar comment
@swift-ci please test macOS platform |
@swift-ci test macos |
We may not invoke
fileSystemRepresentation
on an empty string as per the API contract for the function. Add guards to prevent that. In order to make this behaviour consistency more visible, reorder the constructors to collate the absolute path and relative path handling.