Skip to content

utils: be more flexible about path separators #23764

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
Apr 3, 2019

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Apr 3, 2019

The path separator on Windows is \ and the path separator on Linux,
android, macOS is /. Permit both sets of path separators.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

The path separator on Windows is `\` and the path separator on Linux,
android, macOS is `/`.   Permit both sets of path separators.
@compnerd
Copy link
Member Author

compnerd commented Apr 3, 2019

CC: @jrose-apple

@compnerd
Copy link
Member Author

compnerd commented Apr 3, 2019

@swift-ci please test

@compnerd compnerd merged commit b3a2e40 into swiftlang:master Apr 3, 2019
@compnerd compnerd deleted the regexes-can-solve-everything branch April 3, 2019 22:42
@jrose-apple
Copy link
Contributor

I don't think this is safe! What if a pattern uses a / inside a character class?

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.

2 participants